delete_milestone

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds useful behavioral context beyond the annotations by disclosing that deleted milestones are moved to the trash and can be restored later, clarifying the soft-delete behavior.

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 short and front-loads the operation, but the first two sentences are redundant: 'Delete a milestone. Delete a milestone using its unique identifier.' The third sentence adds new value, so structure is adequate but not maximally 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?

For a single-parameter delete tool with annotations covering safety and no output schema, the description is mostly complete. It explains soft deletion and recovery, though it could clarify the identifier's format or expected scope.

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 reported as 0%, so the description should compensate. It says deletion uses the milestone's 'unique identifier,' which maps to the milestoneId parameter, but adds no format, type, or path details beyond what the schema property already names.

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 states a specific verb and resource: 'Delete a milestone.' It clearly identifies the operation, but it does not distinguish this tool from sibling alternatives like post_batch_delete_milestones or restore_milestone.

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 offers no explicit guidance on when to use this tool versus alternatives such as restoring or batch-deleting milestones. It implies deletion is recoverable, but provides no conditions or exclusions for tool selection.

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