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

With no annotations, the description carries the full burden and does disclose real behavior: it is a read ('Get'), it returns an error when the case is absent, and it flags conditional data availability with 'where published' for parties/counsel. It does not cover auth, rate limits, or result-size/pagination behavior, which keeps it from a 5.

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 sentences, front-loaded with the action and followed by the payload enumeration, which is valuable because there is no output schema. No filler, no repetition of the tool name.

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 single-parameter lookup with no output schema, the description compensates by spelling out the returned fields and the failure mode. Still missing is any hint of depth limits or whether decisions/documents are truncated, but nothing critical to a correct call is absent.

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?

One parameter with 100% schema description coverage, including format examples ('UPC_CFI_196/2025', '[2026] EWHC 2235 (Pat)'), so the schema already does the work. The description adds nothing about the identifier beyond referring to 'one case'; baseline 3 applies.

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 verb and resource ('Get the recorded details of one case') and enumerates the domain content returned: court, action type, patent number, parties, counsel, decisions/documents with date, type, outcome. This makes the scope clear against the search/list siblings, though it never names an alternative to differentiate explicitly.

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: the required case_number and the 'returns an error if the case is not in the database' note suggest a direct by-identifier lookup, but there is no explicit when-to-use, no prerequisite (e.g. where to obtain a case number), and no naming of search_european_dockets as the discovery alternative.

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