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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the content of the response (four count categories), which is useful because no output schema exists, but it does not say whether counts are live or cached, or whether any authentication scope is needed.

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 sentence with no padding; every clause maps to a returned count. The phrase 'how many passages are checked' is slightly ambiguous about what 'checked' means, which keeps it from a 5.

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 no-parameter statistics tool with no output schema, the description does cover what is returned by naming the four count categories. It stops short of describing the shape of the response or whether counts reflect the full archive or the caller's permissions, which leaves a real gap for an agent planning to use the result.

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 zero parameters, so the baseline is 4. Nothing in the description contradicts the empty schema, though it could have said explicitly that the call needs no arguments and covers the whole archive.

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 states a specific resource and scope: counts of passages, organizations, speakers, and checked passages held by the archive. It is clearly an aggregate/statistics tool, which separates it from the sibling getters, listers, and search tools, though the verb is expressed as a question rather than a named action.

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?

Usage is only implied: an agent can infer this is the call to make when it wants archive-wide totals rather than individual records. There is no explicit when-to-use statement, no mention of alternatives such as list_organizations for enumeration, and no prerequisites.

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