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

Annotations already establish readOnly, idempotent, non-destructive behavior. The description adds meaningful beyond-annotation context by warning that live PACER search fees are passed at cost and by stating the returned fields (court, docket, title, filing date). No contradiction with annotations.

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?

Three sentences pack purpose, scope, cost warning, return fields, and a concrete invocation example without fluff. The most important action is front-loaded, and every sentence earns its place.

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?

For a 3-parameter search tool with no output schema, the description covers the operation, fees, and return shape. It could be slightly richer about valid court_region values or limits, but nothing essential is missing for invoking it correctly.

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%, so the schema already documents party_name, _apiKey, and court_region. The description's worked example reinforces the credential format and shows a court_region value, but it does not materially add semantics beyond the schema.

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 a specific action ('Search federal PACER dockets by party') and enumerates the court types covered, so an agent understands the core operation. It does not explicitly compare itself with sibling docketalarm_search or docketalarm_get_docket, so sibling differentiation is implicit rather than stated.

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?

The 'live party-name search' phrasing and the fee pass-through note imply the intended use case: a live PACER lookup by party name. However, there is no explicit guidance about when to choose this over docketalarm_search, docketalarm_get_docket, or another sibling, and no exclusions.

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