delete_milestone

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, idempotentHint=true, and openWorldHint=true. The description adds no additional behavioral context beyond the explicit action, such as whether deletion is permanent, cascades to related data, or has side effects. Since it contributes nothing beyond the annotations, it fails to enhance transparency.

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, focused sentence with no redundant words. It is front-loaded with the action and resource, making it highly scannable and concise.

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 the simplicity of the tool (2 required params) and the presence of annotations covering destructive and idempotent behavior, the description is minimally adequate. However, it lacks any contextual detail about the operation's effects, such as permanence or impact on related data, which would be valuable for an agent deciding to invoke it.

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 100%, with each parameter given a basic description ('the id of the project' and 'the id of the milestone'). The tool description does not add any meaning about how these parameters relate or behave. Baseline for high coverage 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 'Delete a milestone' uses a specific verb (delete) and resource (milestone), making the tool's purpose immediately clear. It distinguishes itself from sibling tools like get_milestone, list_milestones, and update_milestone, which operate on the same resource but with different actions.

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, nor any conditions, prerequisites, or exclusions. There is no mention of situations where deletion might be inappropriate (e.g., milestones with associated work packages or dependencies).

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