remove_milestone

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It identifies the action as a destructive delete but does not state whether deletion is permanent, reversible, or if there are any side effects, permissions, or blocking conditions. The note about completed milestones implies a constraint but does not explicitly state what happens if attempted.

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 two sentences, front-loaded with the primary action, and free of filler. Every word earns its place, conveying purpose and usage constraint efficiently.

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 simple single-parameter delete tool, the description covers purpose and usage adequately. However, the lack of any behavioral details (e.g., irreversibility, refusal conditions) leaves gaps, especially given no annotations or output schema exist to supplement.

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 schema covers 100% of parameters with a clear description ('Milestone ID to remove'). The tool description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 tool deletes a milestone, specifically for 'cancelled or mistaken' ones. It distinguishes from sibling tools like complete_milestone by noting completed milestones should be kept.

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?

Explicit guidance is given: use for cancelled or mistaken milestones, and do not use for completed milestones since they serve as project history. This effectively differentiates from complete_milestone and update_milestone.

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