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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds a useful inventory of what the record contains (rulings, parties by side), but says nothing about missing data, not-found handling, or completeness of the returned record.

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?

A single dense sentence that front-loads the core contents with no filler. It is a noun phrase rather than a full sentence, which slightly reduces clarity but not efficiency.

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?

An output schema exists, so the description need not explain return shapes; listing the major data categories is enough for an agent to decide whether to call. Only edge-case behavior (unknown docket number) is unaddressed, and that is minor given the annotations and schema.

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 both docket_number and the 'purpose' field are documented in the schema, including a format example. The description adds no parameter-level detail beyond that, which is the baseline when the schema does the work.

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 fragment 'One case: dates, disposition, trial, verdict and offer amounts...' makes clear this retrieves a single case record and enumerates its contents. The singular scope implicitly distinguishes it from search_cases, though no verb is used and the sibling is never named.

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?

Usage is only implied by the singular 'One case' against the search_cases sibling; there is no explicit statement of when to use this versus searching. The agent must infer that a known docket number routes here.

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