assign_items_to_iteration

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. While 'bulk assign' implies a write/mutation operation, it doesn't specify permissions required, whether the operation is reversible, what happens to previously assigned iterations, or any rate limits. This leaves significant behavioral gaps for a mutation tool.

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 functionality without unnecessary words. It's appropriately sized for what it communicates, though what it communicates is limited in scope.

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?

For a mutation tool with 4 parameters (0% schema coverage), no annotations, and no output schema, the description is inadequate. It doesn't explain what 'items' are (issues, tasks, etc.), what format IDs should use, what happens on success/failure, or provide any error handling context, leaving the agent poorly equipped to use this tool correctly.

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?

With 0% schema description coverage for all 4 parameters, the description provides no semantic information about what 'projectId', 'itemIds', 'iterationId', or 'fieldName' represent. The description mentions 'items' and 'iteration' which loosely map to two parameters, but doesn't explain their formats, relationships, or why 'fieldName' might be optional when others are required.

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 ('bulk assign') and target ('multiple items to a specific iteration'), providing a specific verb+resource combination. However, it doesn't differentiate from potential sibling tools like 'add_issues_to_sprint' or 'set_field_value' that might handle similar assignment operations, preventing 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, constraints, or compare it to sibling tools like 'add_issues_to_sprint' or 'set_field_value' that might handle similar operations, leaving the agent with minimal context for proper tool selection.

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