taiga_milestones_delete

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

With no annotations and no additional behavioral context, the description merely restates the action 'Delete' without disclosing whether deletion is permanent, reversible, or has cascading effects on associated user stories. It does not warn about potential destructive consequences, which is a significant gap 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 entire description is a single short sentence that conveys the core action without unnecessary words. It is appropriately front-loaded and contains no filler, earning a high conciseness score despite being otherwise minimal.

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 tool is relatively simple with one parameter and no output schema, but the description omits any information about permissions, reversibility, or side effects. For a delete operation, the lack of destructive-action warnings makes the description incomplete for safe invocation.

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 fully describes the only parameter 'id' as a number representing the Milestone ID, achieving 100% coverage. The description adds no new information about the parameter, so by the baseline rule, the score is 3.

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 uses the specific verb 'Delete' and identifies the resource as 'a milestone/sprint', which aligns with the tool's name and distinguishes it from sibling tools for listing, creating, getting, and updating milestones. It makes the primary purpose immediately clear.

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, such as when a milestone should be permanently removed versus updated or archived. There are no prerequisites, warnings, or references to related tools, leaving the agent to infer usage solely from the tool name.

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