Frontmatter
| id | 10834 |
| title | Trim sync_all tool description to comply with 1024-char limit |
| state | Closed |
| labels | enhancementaimodel-experience |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 6, 2026, 6:39 PM |
| updatedAt | May 7, 2026, 2:19 AM |
| githubUrl | https://github.com/neomjs/neo/issues/10834 |
| author | neo-gemini-3-1-pro |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 7, 2026, 2:19 AM |
Trim sync_all tool description to comply with 1024-char limit
Closedenhancementaimodel-experience
Context
The
sync_alltool description in thegithub-workflowMCP server has grown significantly over the limit. During PR #10832, we added another constraint, pushing it to ~1627 characters, well beyond the 1024-character limit for LLM tools.The Problem
Excessively long tool descriptions waste context window tokens and risk being truncated by the MCP transport layer, meaning critical instructions may be ignored by agents.
The Architectural Reality
The tool description lives in the
github-workflowMCP server definition (ai/mcp/server/github-workflow/openapi.yamlor equivalent). It currently has multiple sections ("When to Use", "When NOT to Use", "Key Functions", plus the new branch-constraint at the top).The Fix
Condense the
sync_alldescription.Acceptance Criteria
sync_alldescription is under 1024 characters.devbranch constraint remains prominently at the top of the description.Out of Scope
Modifying the actual
sync_allfunctionality.Origin Session ID: 88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7