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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds real behavioral value beyond them: the chunking/pagination protocol (offset 0, fixed length cap, carry next_offset unchanged) and the bounded-fetch guarantee.

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 tight sentences, front-loaded with the core action, then pagination, then the exclusion. No redundant restatement of the name or title, and every sentence carries an instruction.

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 return-value description is unnecessary, and the pagination mechanics are explained. Enough to call the tool correctly; the only soft spot is the ambiguous next_offset reference that an agent must map onto the response.

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 baseline is 3, but the description adds workflow meaning the schema lacks: the exact source of collection/id/generation values and the offset/length progression. It notably references next_offset, a response field not present as a parameter, which is useful but slightly confusing.

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 ("Read official record text") and ties the operation to values returned by search, which implicitly separates it from the sibling search/detail tools. However it never names an alternative tool, so the sibling differentiation is by inference rather than explicit.

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 operational guidance: use the exact collection/id/generation from search, start at offset 0 with length 1–16,000, then reuse next_offset. It also states an exclusion ("Does not fetch arbitrary URLs or paths"). It stops short of naming alternatives such as detail for metadata.

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