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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds real behavioral context beyond that: it deliberately surfaces negative results ('explicit not-covered rows') and asserts authority ('source of truth'), which tells the agent not to second-guess or cross-check these figures.

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?

One front-loaded sentence that answers 'what do I get' before the closing authority claim. The enumerated clause is dense but every item is a distinct return category, so nothing is wasted.

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 zero-parameter, read-only inspection tool with no output schema, the description enumerates the returned sections well enough that an agent knows what to expect. Minor gap: it does not state the response shape (single object vs. list of per-source entries), but that is low risk here.

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 and the schema confirms an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter guidance is needed or missing.

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?

It names the resource (OpenRemedies coverage) and enumerates the concrete contents: source registers, jurisdiction span, per-source freshness, jurisdiction matrix, evidence counts. That is far more specific than the name alone. It does not, however, explicitly distinguish itself from sibling evidence tools like get_evidence or recent_changes.

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 source of truth for coverage figures' implies you should call it when you need authoritative coverage numbers. But there is no explicit when-to-use, when-not-to-use, or named alternative — the agent must infer that this is the scoping/discovery call to make before using evidence tools.

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