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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral detail beyond those: exact-page matching, list-everything behavior when page is omitted, and the return shape being the same as caselaw_search.

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?

Three short sentences with no filler. The core purpose is front-loaded, followed by a concrete example and the key page-omission nuance. Every sentence earns its place.

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 lookup tool with strong annotations, an output schema, and well-named parameters, the description covers the essential behavior: exact citation lookup, page omission behavior, and output compatibility with caselaw_search. Remaining details like pagination and response format are sufficiently represented by the schema and defaults.

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?

The description adds meaningful semantics for the core params: journal and year through the example, and especially page, whose omission changes the result set. However, schema description coverage is only 33%, and limit, offset, and response_format receive no descriptive help from either the schema or the description.

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 action and resource: 'Find the judgment(s) at an exact law-report citation.' The example with journal='PLD', year=1995, page=34 makes the lookup concrete, and referencing caselaw_search helps distinguish this citation-lookup tool from search-based siblings.

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?

Gives clear invocation context: use it when you have an exact law-report citation, and explains the important behavioral alternative of omitting page to list everything in a journal+year. It does not explicitly name sibling alternatives or say when not to use them, so it falls short of a 5.

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