list_queue_sprints

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

Discloses ordering by start date and status field, but no annotations are present. Description does not cover potential side effects, permissions, rate limits, or pagination behavior.

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: first explains what the tool does, second gives usage examples. No wasted words, front-loaded with purpose.

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?

Covers purpose and usage adequately for a simple list tool, but lacks details on parameter semantics and return format. No output schema provided, so description could have helped more.

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 only parameter 'queue' is not described in the schema (0% coverage) and the description only says 'for a queue' without clarifying whether it expects an ID or name, or what format is expected.

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 it lists sprints for a queue, ordered by start date with status, and gives specific use cases (find current sprint ID, resolve sprint name). Distinguishes from sibling tools as no other sprint-related tools exist.

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?

Provides explicit use cases ('Use this to find the current sprint ID or to resolve a sprint name'), but does not mention when not to use it or alternatives. However, no alternative sprint tools exist among siblings.

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