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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context: only public cases are accessible, results mirror the case page, and disposition appears only when recorded. This goes beyond the annotations without contradicting them.

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 one dense sentence with the action and identifier format front-loaded, followed by a precise field list. Every clause adds useful information; there is no 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 one required parameter, no nested objects, and safety fully covered by annotations, this description is nearly complete. It lists the return content despite the absence of an output schema. Only edge-case handling and explicit failure behavior are omitted, which is a minor gap for a read-only resource.

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 full burden. It supplies a canonical URL template and indicates the parameter is the case identifier. The description does not cover invalid or not-found URLs, but it gives enough semantic grounding for correct invocation.

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 uses a specific verb and resource ('Get a public case') and identifies the exact input form (Docket Nexus URL). It enumerates the returned fields, which clearly differentiates it from sibling tools like get_case_docket, get_document, and search_cases.

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 URL and 'public case' wording imply when this tool is appropriate, but the description never explicitly contrasts it with siblings such as get_case_docket or states when not to use it. The usage context is clear enough to guess, but not explicit enough to reliably route an agent.

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