Delete milestone

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond that — no mention that deletion is permanent, that issues/MRs referencing the milestone are affected, or what permissions are required.

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 single short sentence is front-loaded and wastes no words, but that is because it says almost nothing; brevity here reflects under-specification rather than disciplined editing.

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 destructive, open-world mutation with six opaque parameters and no output schema, the description is far too thin. An agent cannot determine from it which identifiers to pass, whether an empty params object is accepted, or what the consequences of the call are. Only the annotations supply meaningful context.

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 0% across six parameters, and the description compensates for none of it. Critically, it never explains how the milestone is identified (project_id plus milestone_id or title) — and the schema marks no parameter as required, so an agent has no stated basis for deciding which fields to supply. The unrelated-looking data/description/state_event parameters are left entirely unexplained.

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 is effectively a restatement of the tool name and title: 'Delete a project milestone' adds only the word 'project' beyond what 'gitlab_delete_milestone / Delete milestone' already convey. It does not distinguish this tool from the many sibling delete tools (delete_epic, delete_label, delete_release), nor clarify that the milestone is project-scoped rather than group-scoped.

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?

There is no guidance on when to use this versus gitlab_update_milestone (e.g. closing a milestone via state_event) or versus deleting related entities. No prerequisites, no warning about irreversible loss of milestone association with issues/MRs, no mention of alternative workflows.

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