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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low. The description usefully adds the data provenance (CourtListener) and confirms results are sorted/limited by recency, but says nothing about pagination, result shape, or what 'recent' concretely means.

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?

Two tight sentences with the resource and source front-loaded, no filler. The 'filter by party, court, or Nature of Suit' clause partly restates schema fields, which keeps it from a perfect score, but the NOS glossary earns its space.

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 low-complexity read-only search with full schema descriptions, complete annotations, and no output schema, the description covers source, scope, and the non-obvious parameter vocabulary. The main untouched gap is the undefined recency window and the overlap with courts_by_party.

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%, giving a baseline of 3, but the description goes beyond the schema by decoding the opaque Nature-of-Suit codes (850=securities, 830=patent, 410=antitrust, etc.), which the schema only lists as numbers. That mapping genuinely helps an agent choose the right filter value.

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 resource (recent federal court dockets) plus the upstream source (CourtListener), so the agent knows exactly what it retrieves. It does not, however, differentiate itself from the close sibling courts_by_party, which overlaps on the party filter.

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?

There is no when-to-use statement, no exclusions, and no routing to alternatives such as courts_by_party or courts_recent's nondocket siblings. The filter list reads as a feature enumeration rather than invocation guidance.

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