Bounded native pages

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value beyond them: the hard 5-page cap and the continuation rule (provider metadata drives continuation; absent metadata yields an explicit unknown continuation), which tells the agent how to interpret a truncated result.

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 tightly written sentences with the scope constraint front-loaded and no filler. The second sentence is somewhat dense but each clause (continuation source, missing-metadata outcome) 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 tool with a nested-object parameter, 0% schema coverage and no output schema, the description is too thin: it omits how 'arguments' must be formed and what a page result contains. The continuation note is the only substantive detail.

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% with three parameters including a nested 'arguments' object, so the description must carry the load. It only loosely maps 'at most five pages' to max_pages and never explains the operation enum or the shape/semantics of the arguments object, leaving the most error-prone parameter undocumented.

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 (Read) and resource (pages of a supported paginated named operation) with an explicit bound of five pages. It does not name which operations are 'supported' (the schema enum does that) nor distinguish itself from the sibling list_zones/list_dns_records tools it presumably wraps, so it falls short of a 5.

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 when-to-use guidance: it never says why an agent should call query_pages instead of the direct list_zones / list_dns_records siblings, nor when a single-page versus multi-page read is appropriate. Only the continuation behavior is implied, which is behavioral rather than selection guidance.

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