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

Annotations already establish a safe read-only operation, so the description adds value by disclosing the data source (CourtListener), the $0.10 USDC cost, and the cryptographic attestation with verification URL. It does not cover rate limits or result counts, but for a read-only, low-risk call the added behavioral context is meaningful.

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 description is compact and front-loaded: core behavior first, then use case, then cost and verification details. No sentence is redundant, though the attestation and fee details are secondary to invoking the tool correctly.

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 helpfully lists key return fields: open cases only, last filing date, nature of suit, and most active courts. However, it omits expected result shape, pagination behavior, and the meaning/effect of the optional court parameter, so the context is adequate but incomplete.

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 0%, so the description carries the burden of explaining parameters. It implicitly maps party_name to 'a named party,' but it provides no semantics for the optional court parameter, leaving the agent to guess whether it filters results or appears only in output.

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 clearly states a specific action and resource: retrieving active federal dockets for a named party, including open-case scope, last filing date, nature of suit, and most active courts. It differentiates from siblings by emphasizing 'open cases only' and 'federal dockets,' but it does not explicitly name or contrast an overlapping sibling like get_party_litigation_profile.

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 description gives an explicit use case: 'Use for ongoing litigation monitoring.' This tells the agent when the tool is appropriate. However, it does not state when not to use it or name alternatives, such as get_party_litigation_profile or get_federal_court_cases.

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