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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description's contribution is enumerating the returned payload (printed form, conversion, evidence level, conditions, source locations/passages), which is genuinely useful given there is no output schema, but it is phrased loosely and omits behavior for an unknown or unprovable claim_id.

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 a single sentence, which is efficient, but the front-load ('Everything behind one value') is vague and the trailing list — especially '(and the passage where we have it)' — is hard to parse. Compactness is achieved at the cost of readability.

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 does attempt to sketch the return payload, which is the right instinct for a provenance-lookup tool. It remains too imprecise to tell an agent what fields to expect or how failures (missing claim, no evidence) manifest, so it is adequate rather than complete.

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% and the single parameter claim_id is documented as coming from list_claims, so the schema carries the semantics. The description adds nothing about the identifier, so 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?

The description conveys that the tool surfaces all provenance behind a single claim/value (source form, converted form, evidence level, conditions, sources), which is a recognizable purpose. But it never uses a verb like 'retrieve' or 'return' and never names what a 'value'/'claim' is relative to siblings such as list_claims or get_material. An agent can infer the intent, but only after reading the whole list.

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?

There is no statement of when to call this versus compare, get_material, or list_claims, and no prerequisites or exclusions. The only implicit cue is that a claim_id comes from list_claims, which appears in the schema rather than the description.

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