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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds substantial context the annotations cannot: data provenance (CourtListener, Free Law Project, RECAP index), caching semantics ('as the index stood on the date given'), and an interpretive caveat that presence implies neither merits nor outcome. It also discloses a coverage limit (no state courts).

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 answer content and scope are front-loaded, and the closing caveats are short and load-bearing. The opening sentence is a long multi-clause run-on that could be split, but no sentence is filler.

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 carries the return shape itself — court, filing date, docket number, nature of suit, and a docket link — plus ordering (newest first) and the data-freshness caveat. An agent has everything needed to call it and interpret the result.

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 coverage is 100% so the baseline is 3, but the description adds matching semantics beyond the field docs: 'make' must be a named party while 'model' and the vehicle system are matched against case text, and omitting 'system' answers every system on file. That is real added meaning, though it doesn't restate the enumerated slug list.

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 verb+resource+scope: federal lawsuits in the RECAP docket index that name a vehicle manufacturer as a party and mention a model in a named system. It also enumerates the case types (product-liability, warranty, lemon-law, class) and returned fields, which cleanly separates it from siblings like check_recalls, lookup_bulletin and get_trims.

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?

It states clear context (researching manufacturer litigation) and bounds the domain with exclusions — state-court cases are not indexed, and a docket's presence says nothing about merits or outcome. However, it never routes the agent to an alternative tool or states when *not* to call this one, so it stops short of full when/when-not guidance.

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