Manage Milestones

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds no behavioral context beyond listing operations: it does not explain what delete removes, permission requirements, side effects, or rate limits. It does not contradict the annotations.

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 efficient sentences with the operation list front-loaded and no filler. However, the second sentence is largely redundant with the schema, so it is not maximally useful.

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?

This is a complex, destructive, multi-operation tool with 12 parameters, yet the description gives no per-action parameter mapping or operational context. Annotations cover the safety profile, but the description remains too thin for an agent to call actions correctly without inspecting the schema.

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 only 8%, with 12 parameters and just the `action` field documented in the schema. The description does not compensate by explaining the roles of sort, limit, state, status, dueDate, daysAhead, direction, description, milestoneId, or includeIssues, nor which parameters belong to which action.

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 resource (milestones) and enumerates the supported operations: create, list, update, delete, metrics, overdue, and upcoming. This clearly distinguishes it from siblings like manage_issues or manage_project, though it does not explicitly name those alternatives.

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 only guidance is 'Use the `action` field to select the operation,' which merely restates the schema. It does not explain when to choose each action, which parameters apply to which operation, or when to prefer this tool over sibling tools.

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