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

Goes well beyond the annotations by disclosing cost ($0.01 per call), the payment rail (USDC on Solana via x402), the exact challenge-then-retry flow with the _meta["x402/payment"] key, and an HTTP equivalent endpoint. Missing only whether results are cached/snapshot-bound or how pricing failures surface. No annotation contradiction: readOnlyHint=false is consistent with a metered, payment-mutating call rather than a free read.

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-loads the capability, then condenses payment logistics and the HTTP mirror into one tight follow-on sentence. Every clause carries information; no filler or repetition of the schema.

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?

Adequate for invocation: cost, payment handshake, and endpoint are covered, and there is no output schema to explain. However, with one undocumented optional parameter and no sense of result size/shape or whether the slice is static, an agent still lacks enough to predict or parameterize the call fully.

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?

The single parameter 'generation' has an enum of two dates but zero schema description coverage, and the description never explains what a generation represents or what omitting it does (it is optional). The phrase 'seeded bulk slice' gestures at the concept without defining it, so the agent cannot confidently choose a value.

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 operation: computed aggregates over a seeded bulk slice, enumerating the aggregate families (judges per court, totals, disclosures by year/report type, investment row totals). This clearly distinguishes it from the sibling record-level tools (courts_court_record, courts_judge_record, courts_disclosure_record, courts_changes), though it does not name those alternatives explicitly.

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?

No guidance on when to pick this over the sibling courts_* record tools or courts_changes — the agent must infer from the word 'aggregates'. The only usage-like content is the payment retry mechanics, not tool selection criteria.

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