iterations-delete

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

The description explicitly notes irreversibility ('cannot be undone'), which adds behavioral context beyond the schema. However, it does not mention any side effects (e.g., deletion of associated stories) or authorization requirements.

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 extremely concise, consisting of two short sentences with no unnecessary words. Every part adds value.

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?

The description lacks critical context about the tool's impact on related entities (e.g., what happens to associated stories or tasks), and provides no information about authorization or output. Given the permanent nature of the operation, more completeness is expected.

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?

The input schema already provides a description for the only parameter ('Iteration ID'), achieving 100% coverage. The tool description does not add additional semantic value about the parameter beyond what the schema offers.

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 ('Delete an iteration') and emphasizes permanence ('cannot be undone'). It uses a specific verb+resource combination, distinguishing it from sibling tools like 'iterations-create' or 'iterations-update'.

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?

No explicit guidance on when to use this tool versus alternatives, nor what prerequisites or consequences exist (e.g., whether iteration must be empty). The implied usage is simply when deletion is desired, but the lack of exclusions or alternatives hinders decision-making.

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