get_backlog_summary

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

There are no annotations, so the description must carry the full burden. It conveys only that the tool returns aggregate statistics, with no detail about whether this is read-only, how the aggregation is scoped, what shape the statistics take, or whether any state is affected. This is minimal disclosure for a tool with no output schema.

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 front-loaded sentence with no filler or repeated information. It is appropriately compact for a parameterless operation, though it could sacrifice some brevity to add distinguishing details without becoming bloated.

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?

Against a large sibling set with many backlog-related tools, this description is too thin to let an agent reliably select it. With no output schema and no detail about scope or return value, the agent cannot determine what aggregate statistics will be produced or how they differ from get_backlog or get_completion_stats.

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?

There are zero parameters and the schema already covers this completely with an empty properties object. With no parameters to document, the description does not need to add parameter semantics; the baseline 4 for a parameterless tool 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?

The phrase 'Get aggregate backlog statistics' identifies a verb and resource, and 'aggregate' suggests a high-level summary rather than a list. However, it is vague: it does not specify what statistics are returned or how this differs from several similarly named siblings such as get_backlog, get_subject_backlog, and get_completion_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?

No usage conditions or alternatives are mentioned. The description does not say when to choose this over get_backlog, get_subject_backlog, get_chapter_backlog, or get_completion_stats; only the word 'aggregate' hints at a distinction, which is left to inference.

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