taiga_milestones_stats

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

No annotations are provided, so the description is the sole source of behavioral information. It indicates a read-only 'Get' operation and that it returns stats, but does not disclose whether specific permissions are needed, the exact response structure, or any side effects. The additional context beyond the name is minimal (the 'burndown' example).

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 sentence with no filler or repetition. 'Get milestone/sprint stats (burndown, etc.)' conveys the core purpose efficiently. The use of 'etc.' is slightly vague but does not detract from conciseness.

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 one-parameter tool and the lack of an output schema, the description would need to explain what stats are returned to be fully complete. It only offers the vague example 'burndown, etc.', which may leave an agent unsure about the exact return data. The read-only nature is implied but not explicitly stated, though 'Get' helps.

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 one parameter (id) with a clear description 'Milestone ID', and the schema description coverage is 100%. The tool description does not add any parameter-related information, but the baseline for high schema coverage is sufficient. Thus it neither helps nor hurts.

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 clearly states the tool retrieves stats for a milestone/sprint, with 'burndown' as an example. This distinguishes it from sibling tools like taiga_milestones_get, which fetches the milestone itself. However, 'etc.' leaves some ambiguity about the full scope of stats.

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 this tool is for obtaining sprint statistics but does not explicitly state when to prefer it over similar tools like taiga_milestones_get or taiga_projects_stats. There are no exclusions or alternative references. Usage context is only implied by the word 'stats' and the example 'burndown'.

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