get_sprint_tasks

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds behavioral detail that both direct sprint list tasks and tagged tasks are returned, which is beyond the schema. No contradictions with annotations; however, it doesn't mention ordering or pagination, though that's less critical for this simple read operation.

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 three short sentences: a clear purpose statement, a scope clarification, and parameter explanations. It is front-loaded with the main action and contains no redundant text.

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?

For a simple read-only list tool with an output schema present, the description covers purpose, scope, and parameters. Minor gap: it doesn't state behavior when no current sprint exists or whether the output is exhaustive, but these are edge cases given the richness of sibling tools and context.

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?

Both parameters (assignee, status) are described in the tool description with usage details: 'me' for current user and example statuses like 'in progress'. Since the schema has no descriptions (0% coverage), the description fully compensates and adds meaning beyond the raw schema.

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 'List tasks in the current sprint, optionally filtered' with a specific verb and resource. It also adds scope detail by mentioning both direct sprint list tasks and tagged tasks, distinguishing it from sibling tools like get_sprint_report or get_my_tasks.

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 usage for retrieving current sprint tasks but does not explicitly contrast with alternatives such as get_sprint_report or get_list_tasks. There are no exclusions or 'use when' guidance, so while the context is clear, it lacks explicit alternative differentiation.

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