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 of behavioral disclosure. 'List milestones' offers no insight into whether this is a read-only operation, its potential side effects, authentication requirements, rate limits, or output format. For a tool with three parameters and no output schema, this lack of behavioral context is a significant gap.

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 extremely concise at two words, with zero wasted text. It is front-loaded and efficiently states the core action, though this brevity comes at the cost of completeness. Every word earns its place by directly addressing the tool's function, albeit minimally.

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 complexity (three parameters, no output schema, no annotations), the description is grossly inadequate. It does not explain what the tool returns, how parameters affect results, or behavioral traits. For a list operation with filtering and sorting capabilities, this leaves critical gaps in understanding how to use the tool effectively.

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 input schema has 0% description coverage, meaning parameters 'status', 'sort', and 'direction' are entirely undocumented in the schema. The description adds no information about these parameters—their meanings, allowed values, or usage—failing to compensate for the schema's deficiencies. This leaves the agent with no semantic understanding of the inputs.

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 'List milestones' is a tautology that merely restates the tool name without adding meaningful context. It specifies the verb 'list' and resource 'milestones' but lacks any detail about scope, format, or what distinguishes it from sibling tools like 'get_milestone_metrics', 'get_overdue_milestones', or 'get_upcoming_milestones'. This minimal statement fails to clarify the tool's specific purpose beyond the obvious.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it reference sibling tools that might serve similar purposes (e.g., filtered milestone queries). Without such information, an agent cannot make informed decisions about tool selection.

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