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

Annotations only give the generic read/write/idempotency flags, and the description adds genuinely non-obvious behavior: a $0.01 per-call charge, the x402 flow (call once, receive PaymentRequired, retry with _meta["x402/payment"]), the HTTP fallback endpoint, and the data vintage (quarterly bulk snapshot). It does not explain latency, failure modes, or what happens if payment is invalid, so it is 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?

Two sentences, front-loaded with purpose and scope before the payment mechanics, with no filler. The payment parenthetical is dense but operationally necessary, though it could be trimmed by pointing at a payment convention.

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 carries the burden of describing returns, and it does so only in passing ('courthouses and appeals-to edges'). The generation/snapshot-selection parameter and the record's field shape remain undocumented, which leaves gaps for a 2-parameter tool that costs money per call.

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 0% and the description only restates court_id as 'by court id' with no format or validation detail. The 'generation' parameter — which selects between the 2026-06-30 and 2026-09-30 snapshots — is never mentioned, leaving the agent to infer its meaning from the enum values alone.

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 names the exact resource (court record) and its key (court id), and adds what the payload contains — courthouses and appeals-to edges — which implicitly separates it from courts_judge_record, courts_disclosure_record, courts_stats and courts_changes. It lacks an explicit verb and never names a sibling, so it falls short of the top mark, but an agent can still tell what it retrieves.

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 only implied: the reader infers 'use this for a single court's record' and the payment paragraph explains how to invoke it, not when to pick it over courts_changes or courts_judge_record. There is no when-to-use, when-not-to-use, or alternative routing guidance.

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