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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: data lineage (CourtListener), coverage scale (1M+ documents), cost ($0.50 per call), and temporal scope (active and historical). No contradiction with the annotations — a read-only tool that returns docket data is consistent.

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?

The 'Use when' clause is front-loaded, which is good, but the description runs long: a lengthy enumeration of use-case scenarios (contract award, acquisition, investment, board appointment, enterprise partnership), a detailed multi-case example with dollar estimates, and source/cost boilerplate. The example and pricing are genuinely informative, but the scenario list and example could be trimmed without losing signal.

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 correctly carries the burden of describing return values and does list the returned fields plus a concrete example. But it omits semantics for two of three parameters (party_name and years_back), and it never describes return format, pagination, or what 'active status' means operationally. Adequate but with clear gaps for a 3-parameter tool.

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 only 33% — only 'court' is documented in the schema. The description partially compensates for party_name through its example ('Acme Corp' screening), but never explicitly states that party_name is the entity to be screened. years_back is entirely undocumented in both schema and description; its default of 5 and its meaning are never addressed. The description does not close the gap for two of three parameters.

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-resource: 'Returns active and historical federal court dockets across all US district and appellate courts' with the concrete data fields (case names, docket numbers, courts, filing dates, nature of suit, active status). Purpose is unambiguous. However, it does not differentiate from closely related siblings like get_party_litigation_profile, get_federal_case_law, and get_docket_intelligence, any of which an agent might reasonably pick for the stated screening use case.

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?

Explicitly tells when to use: 'Use when screening a company, executive, vendor, or counterparty for federal litigation exposure before a contract award, acquisition, investment, board appointment, or enterprise partnership.' That is a clear trigger condition. But it provides no exclusions or alternative routing, and given siblings like get_party_litigation_profile and get_ofac_sanctions_screening, explicit when-not-to-use guidance would materially reduce mis-selection.

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