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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes beyond them by disclosing the paging contract ('entries are paged by JSON Pointer; next continues the answer') and noting that the reports section includes failures, which tells the agent to expect error data in results. It stops short of describing auth requirements or error behavior.

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 the resource named first and no filler; the paging note is a single useful clause. Terms like 'boundaries' and 'performance' are loose but do not pad the text.

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 6-parameter read tool with no output schema and no schema descriptions, the description covers pagination but omits the return structure beyond the paging token and never explains the required contentHash or how sections filtering interacts with paging. It is usable but leaves meaningful gaps.

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% across 6 parameters, so the description carries the burden; it partially compensates by naming content areas that map to the 'sections' enum (purpose/description, interface, checks, reports) and by implying paging via offset/limit. It says nothing about why contentHash is required alongside name and version, leaving a required parameter unexplained in both schema and 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?

The description identifies the resource (a 'passport' for an exact release) and enumerates its content areas, but uses a noun phrase with no verb and relies on domain jargon ('passport') that an agent cannot resolve from the text alone. It never distinguishes this from siblings such as law_editions, law_report, or law_rules, which plausibly return overlapping release metadata.

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?

There is no statement of when to call this tool versus alternatives, no prerequisite for obtaining name/version/contentHash, and no exclusion criteria. The only operational guidance is about paging, not selection.

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