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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by explaining counts_as_verified semantics and enumerating which statuses (indeterminate, refuted, decayed, withdrawn, redacted, self_declared) force it false. It still omits return shape details such as receipt count or ordering, so it is solid but not exhaustive.

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?

It is front-loaded with the list of returned fields, then details, then status semantics, which is a sensible order. However, the first sentence is a comma-spliced wall of items and the text is dense with internal jargon (dx-1, fw-1, gi-2, verdict_input, relay) that costs parsing effort. Content mostly earns its place, but the packaging does not.

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?

There is no output schema, so the description must explain what comes back, and it largely does: status, tier, cap reasons, one-line relay, receipts, reliance_prior, plus conditional reliance/identity_rule additions. The coverage gap is around the id parameter's accepted forms (claim id syntax), not the return payload.

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 67%, and both optional parameters carry their own detailed schema docs (fresh_within, require_genuine_identity). The description adds nothing about the id parameter or how the optional params alter the response beyond what the schema already says. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb+resource: it returns status, evidence tier, limits, a relay summary and recent receipts for a given claim id. It also marks reliance_prior as display-only, which helps distinguish it from get_reliance_prior. It stops short of explicitly routing an agent away from named siblings, so it is clear but not fully differentiated.

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 never says when to call this tool versus alternatives like get_decay_index, get_track_record or search_claims. The one usage cue ('before a costly or irreversible step') lives in the fresh_within parameter, not the description. An agent must infer that this is the general per-claim status lookup.

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