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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds real behavioral detail beyond them: pagination, kind filtering, flagging of spec divergences, and the evidence fields attached to each record. With no output schema, this return-shape disclosure is genuinely useful, though details like page size limits are absent.

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 dense sentence that front-loads what is returned before the modifiers, with no filler. The parenthetical and trailing clauses are packed but each carries a distinct fact (default version, evidence contents, verbose behavior).

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, the description appropriately describes the returned records and the verbose variant, and mentions pagination, which is what an agent needs to invoke and interpret it. Missing are practical bounds (limit/offset reintroduction beyond schema defaults) and any hint of how divergences relate to the get_divergences sibling.

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?

Schema coverage is 67%, so the schema already documents kind, tool, limit, offset, and version. The description adds meaning only for verbose ('adds response previews'), which the schema leaves undescribed, and reinforces the latest-version default. That is incremental value, not full compensation for the uncovered gaps.

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?

States a specific verb+resource: returning 'every verified claim about an API as structured records', which is concrete and distinguishable from a generic search. However it never names or contrasts itself with close siblings such as search_claims, get_divergences, or get_tool_docs, so the agent must infer boundaries from the returned fields.

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 description notes defaults and filters ('latest version by default', 'filterable by kind') but gives no explicit when-to-use or when-not-to-use guidance against siblings like search_claims or get_divergences. An agent has no stated condition that selects this tool over those.

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