list_milestones

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

No annotations are provided, so the description carries the full burden. It states 'Show' which implies a read-only operation, but it does not explicitly confirm non-destructive behavior, mention permissions, or describe any side effects. The description provides minimal behavioral disclosure beyond the action itself.

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 concise sentence that is front-loaded with the action and resource. It contains no unnecessary words or redundant information, making it highly efficient.

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 tool's low complexity, one optional parameter, and an existing output schema, the description is nearly complete. It clearly states what is returned (milestones and their status). However, it does not explicitly link the 'all milestones' to the 'path' scope, leaving a slight ambiguity about whether the list is project-wide or scoped to the provided root directory.

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 description coverage is 100%, with the 'path' parameter already described as 'Project root directory.' The tool description adds no further meaning to this parameter, so a baseline score of 3 is appropriate. The schema handles the parameter documentation.

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 uses a specific verb ('Show') and resource ('milestones') and adds detail ('and their status'), clearly distinguishing it from sibling tools like list_tasks or list_phases. It unambiguously conveys the tool's function without relying on the name alone.

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 implies when to use the tool (when a user needs to see milestones), but it does not provide explicit context, exclusions, or alternatives among the many sibling tools. There is no guidance on how it differs from list_tasks or list_phases, leaving the agent to infer usage.

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