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

Annotations already declare readOnly/idempotent/non-destructive behavior. The description adds a meaningful boundary ('does not fetch arbitrary URLs or paths') and 'bounded', but does not disclose output shape, pagination behavior, or generation semantics. No contradiction with annotations.

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 short sentences, front-loaded with the core behavior and ending with a guardrail. No filler; every word contributes.

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?

Given five parameters, no output schema, and no parameter descriptions, the description is too thin for an agent to invoke correctly. It omits collection semantics, range/pagination parameters, generation behavior, and return format.

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%, so the description must carry parameter meaning. It only implies 'id' via 'known identifier' and 'official record' for collection, leaving length, offset, and generation completely unexplained. This is insufficient for five parameters.

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 uses a specific verb ('Read'), resource ('official record text'), and scope ('by known identifier'), and adds an exclusion for arbitrary URLs/paths. It is clear, though it does not name a sibling alternative like 'detail' to fully differentiate.

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?

It clearly indicates the intended use case: reading a known official record identifier. It also states when not to use it ('Does not fetch arbitrary URLs or paths'). However, it does not explicitly route to any alternative sibling tool.

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