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

Annotations already cover readOnly, idempotent and closed-world, so the bar is lower, yet the description still adds a genuinely useful caveat: removed items retain only id/date/reason and therefore will not surface in a word search. It also names the possible state values, which helps an agent interpret results rather than just retrieve them.

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?

Purpose is front-loaded in the first clause, followed by return-field detail and one usage sentence. Dense but every clause carries information; the long first sentence is heavy, though nothing is truly redundant.

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 read-only search with no output schema, the description adequately enumerates what comes back and flags the removed-item edge case. The only shortfall is that result ordering and the limit default/interaction with paging are left entirely to the schema.

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 description coverage is 100%, so both parameters (query, limit) are already documented in structured data. The description reinforces that query targets tool/model/feature names but adds no syntax, matching or paging detail beyond the schema, so the baseline 3 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?

States a specific verb and resource ('Search the claims Context Pill has published (the ledger)') and enumerates the returned facets (status, check method, current state, re-check, correction). It distinguishes the tool from siblings implicitly by scope but never names get_latest or list_sources, so an agent must infer the boundary.

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?

'Use it to see whether a specific tool, model or feature claim has been checked' gives a clear positive use case, which is more than implied. However, no when-not condition or alternative tool is mentioned, and with get_latest as a close sibling the absence of routing guidance is a real gap.

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