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 indicates a list operation (read-only) by the verb 'List' and mentions return content (progress/status), but does not explicitly disclose permissions, safety, or data scoping (e.g., filtering by status). Lacks explicit reassurance of no side effects.

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?

Two sentences, front-loaded with the core action, no waste. Every sentence contributes to purpose or output behavior.

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 simple list nature and full schema coverage, the description covers purpose and return semantics (progress/status). It doesn't mention filter options or defaults, but those are present in the schema. For a tool with no output schema, this is adequate, though it could explicitly mention the group parameter's role.

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 100% with detailed descriptions for group, limit, and status. The tool description adds no parameter-specific meaning beyond what the schema already provides, so baseline 3 applies.

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?

Description clearly states 'List milestones for a Clink group', a specific verb+resource+scope. This distinguishes it from sibling tools like get_milestone (singular) and create_milestone. The added 'Shows progress and status of each milestone' further clarifies purpose.

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?

It implies usage: use when you need all milestones for a group. However, it doesn't explicitly contrast with alternatives like get_milestone or mention when not to use. The context is clear but exclusions are absent.

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