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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description's job is lighter. It adds the crucial behavioral trait that exhaustion of the excerpt does not imply full coverage—a key caveat that a raw read tool would not convey. It does not mention error behavior, but the core caveat is well-covered.

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?

The description is compact and front-loads the key action and resource. It uses a warning to emphasize the scope caveat, which is efficient. It could be slightly more structured, but it avoids waste.

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 the tool's moderate complexity (5 params, nested contextRevision) and no output schema, the description does a good job of setting expectations for pagination and coverage. It does not explain the mechanics of offset/marker, but the critical 'why' is covered, and annotations cover safety. It is sufficiently complete for an agent to use correctly.

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 only 20%, so the description must compensate, and it does mention 'Echo contextRevision and nextOffset' which helps explain those parameters. However, it does not clarify the 'marker' parameter (its pattern suggests a marker, but the role of the marker in pagination is not described), nor does it explain 'offset' or the 'limit' defaults. The description adds some value but leaves gaps.

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 clearly states a specific verb ('Read') and resource ('bounded page of a frozen source excerpt') and distinguishes it from full-original pagination. However, it does not name a specific sibling tool that handles full pagination, so differentiation from siblings like helvabase_read_original_page is implied but not 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?

The description explicitly states what this tool is NOT for ('NOT full-original pagination'), provides a clear condition for use (reading from a frozen excerpt), and instructs the agent to report gaps as blockers, which is actionable guidance.

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