add_issues_to_sprint

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an 'add' operation (implying mutation), but doesn't disclose any behavioral traits: it doesn't mention permissions required, whether this is idempotent, what happens if issues are already in the sprint, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a simple tool and gets straight to the point. Every word earns its place in conveying the essential action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what happens after adding issues, error conditions, permissions needed, or relationship to sibling tools. For a tool that modifies data, more contextual information is needed for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description doesn't mention any parameters at all - it doesn't explain what 'sprintId' and 'issueIds' represent, their format, or constraints. While the parameter names are self-explanatory to some extent, the description adds zero semantic value beyond what's already inferable from the schema property names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('add') and target resource ('issues to an existing sprint'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'create_sprint' (which creates new sprints) and 'remove_issues_from_sprint' (which does the opposite operation). However, it doesn't specify what type of 'issues' are being added (e.g., Jira issues, GitHub issues), which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that the sprint must already exist), nor does it differentiate from similar tools like 'assign_items_to_iteration' or explain when to use 'add_issues_to_sprint' versus 'create_issue' followed by this tool. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.