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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds valuable behavior beyond that: 'No API key, no rate limit' and the ordering guarantee 'newest first'. These are not redundant with annotations and improve the agent's understanding of side effects and constraints.

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 a single, concise sentence that front-loads the core action and key constraints. It wastes no words and clearly communicates the essential information without redundancy.

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 read-only listing tool with no required parameters and no output schema, the description covers the core purpose, ordering, optional filter, and operational constraints (no auth, no rate limit). It does not mention the filed_after parameter explicitly, but that is fully covered by the schema. It is sufficiently complete for an agent to call the tool correctly, though it could note the sibling tool for broader search scenarios.

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 each parameter (court, limit, filed_after) is already documented. The description adds only a slight reinforcement for the court parameter via 'optionally limited to one circuit', but it does not elaborate on formats or defaults beyond what the schema provides. Baseline 3 applies due to high schema coverage.

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 the tool lists recent US federal appellate dockets in newest-first order, with an optional circuit filter. It uses a specific verb ('list') and resource, and the 'recent' qualifier distinguishes it from a general search, though it does not explicitly name the sibling tool.

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 implies usage for recent docket listings and mentions the optional circuit filter, but it does not explicitly contrast with federal_appeal_search or state when not to use this tool. The context is clear enough that an agent can infer its purpose, but no exclusions or alternatives are given.

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