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

No annotations are provided, so the description carries the behavioral burden. It implies a passive informational read by describing only summary content, but never explicitly states that it is read-only or side-effect-free, and says nothing about auth or rate limits. The implied safety profile is inferable from the content described, which is why this is not lower.

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, both earning their place: the first enumerates the returned content, the second front-loads the use case. No redundancy with the title or name.

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 is the sole source of return-value information, and it delivers by naming exactly what the summary contains (model counts, field coverage, organisations, inclusion rule). It omits nothing critical for a simple stats call, though a note on read-only behavior would round it out.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly does not waste words on argument syntax.

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: a coverage summary with counts of models, field coverage, organisations, and the inclusion rule. It is clearly distinguishable from the sibling tools (get_model, search_models, search_news, etc.), which are retrieval tools rather than a register meta-summary. No explicit sibling naming, but the purpose is unambiguous.

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?

It gives a clear usage context: use this to judge whether the register can answer a question before querying it. That is a real when-to-use signal, not filler. It does not name alternatives or exclusions, so it falls short of a full 5.

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