tasks_overview

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lighter. It does add genuinely non-obvious context in the word 'derived' — status is computed rather than stored — but says nothing about ordering, scope, or whether closed sprints are included.

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?

A single front-loaded fragment with zero filler — the payload contents come first and nothing is repeated. It is telegraphic rather than a complete sentence, which is efficient but slightly terse even for an overview tool.

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?

With no output schema and no parameters, the description carries the full burden of explaining the return value, and it only partially does so: it lists derived status, counts, and goal but not the item shape or whether sprints include task breakdowns. Adequate to select the tool, thin for predicting its output.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly signals a zero-argument, whole-collection call.

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?

Names a specific resource (all sprints) and the concrete payload it returns: derived status, per-status counts, and the goal. That distinguishes it from single-sprint tools like tasks_sprint, but it never explicitly positions itself against tasks_stats or tasks_list, so the differentiation is inferred rather than stated.

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 phrase 'in one call' implies this is a bulk overview rather than per-sprint retrieval, which hints at when to prefer it. However, there is no explicit when-to-use rule and no named alternative among the 18 siblings, so the agent must infer the boundary itself.

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