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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is the credential and billing disclosure: PACER NextGen credentials required and per-search charges ($0.10/page, capped). This is genuinely useful operational context beyond the structured hints, though rate-limit and pagination specifics remain thin.

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?

Purpose and scope are front-loaded in the first clause, then returns, then cost/credentials, then examples. It is dense but every sentence earns its place; the two examples are slightly verbose.

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 an 8-param search tool with no output schema, the description covers purpose, scope, returned fields, credential requirements, and cost. The only gap versus a sibling is the missing differentiation from pacer_party_search.

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 every parameter fully; the description adds only example values. Baseline 3 is appropriate since the schema does the heavy lifting and the description contributes no new parameter semantics.

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 (Find) and resource (US federal court cases) with clear scope (PACER Case Locator, all district/bankruptcy/appellate courts) and lists the returnable fields. It does not name or distinguish the sibling pacer_party_search, so an agent cannot fully disambiguate the two without inspecting schemas.

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?

Two concrete invocation examples show how to combine party_name/court_id/case_title, which implies usage. However, there is no explicit when-to-use guidance, no exclusions, and no routing to the sibling pacer_party_search, so the conditional logic is left to inference.

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