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

Annotations only declare the coarse safety profile, so the description carries the important extras: data provenance (Free Law Project quarterly bulk snapshot), verbatim field fidelity, staleness signalled via as_of, and a hard $0.01 per-call cost with x402 payment requirements. It stops short of covering failure behavior — e.g. whether a rejected payment or a retry double-charges, and why the call is declared non-idempotent despite being a lookup.

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?

Front-loaded with purpose and field coverage, then provenance, then price/protocol, which is a sensible order with little waste. The x402 parenthetical and the HTTP-equivalent URL are dense but genuinely operational rather than filler.

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 the right work: it enumerates returned field groups and explains the as_of vintage marker, so an agent knows what comes back. The one meaningful hole is the undocumented generation input, which affects whether the returned snapshot matches what the agent wanted.

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 0%, so the description must compensate and it only partly does: 'by judge id' implicitly covers judge_id. The second parameter, generation, with its two-value enum (2026-06-30 / 2026-09-30), is never mentioned — the description references snapshot vintage only as an output field (as_of), not as a selectable input, leaving the agent to guess what generation controls.

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 resource and scope: a full judge record keyed by judge id, with an enumerated field inventory (positions, educations, political affiliations, races, retention events). It is clearly distinguishable in content from siblings like courts_court_record and courts_disclosure_record, though it never names those siblings to make the contrast explicit.

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?

Usage is implied (look up one judge by id) and the payment choreography is spelled out in useful procedural detail (call once to receive the PaymentRequired challenge, retry with payment at _meta["x402/payment"]). However, there is no guidance on when to prefer this over courts_court_record/courts_disclosure_record, no prerequisite about where a valid judge_id comes from, and no guidance on choosing a generation.

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