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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds genuinely useful non-obvious behavior: per-call pricing of $0.002 USDC via x402 on Base/Solana/Arc, and that failed calls are not charged. It also discloses coverage limits (not every PACER filing, not a complete registry). Missing only things like result ordering or rate limits.

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: the first front-loads source and returned fields, the second carries the coverage disclaimer and pricing. Dense but every clause earns its place; the inline field enumeration is slightly list-like but informative.

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 an output schema present and full parameter documentation, the description need not explain return values, and it covers the two things structured fields cannot: cost/payment mechanism and data-coverage caveats. Empty-result or pagination behavior is the only remaining gap, and limit already bounds results.

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%, with both q and limit fully documented including length and range constraints. The description adds nothing beyond 'matching your text', so the 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?

States a specific verb and resource: searching US federal bankruptcy dockets from CourtListener, and enumerates the returned fields (case name, docket number, court, chapter, dates, judge, link). The bankruptcy-specific scope naturally separates it from generic case-law siblings like gov_justia_case_law or gov_caselaw_access, though no sibling is named 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?

Usage is implied by 'matching your text' and the coverage caveat clarifies it is search results only, not a complete registry. However, it never says when to prefer this over the other court-record tools in the sibling list, nor any prerequisites or exclusions beyond the coverage disclaimer.

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