Page a collection

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered without description help. The description says nothing about pagination semantics, byte-truncation of items, or what 'next' means beyond what the schema states. With annotations carrying the safety profile, this is an adequate but unenriched 3.

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, with the verb+resource stated first and the discovery hint last. The long collection enumeration would normally be bloat, but it earns its place because the schema has no enum for that parameter.

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 paginated read tool with no output schema, the description plus the maxBytes parameter text together convey enough to call it correctly. It omits a short note on how to continue paging (using the reported next/index), which is the main remaining gap.

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 83%, so most parameters (text, limit, offset, maxBytes, targetId) are already documented inline. The description adds real value for the one bare parameter, 'collection', by listing its valid values in the absence of an enum, but it gives no extra detail on filtering or paging behavior.

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 ('Page through one named list from the analysis') and enumerates the concrete collections available, so an agent knows exactly what it retrieves. It also implicitly distinguishes itself from hexvero_analyze by naming it as the discovery tool rather than the paging tool.

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?

'Use hexvero_analyze to see which exist' gives explicit routing guidance for discovering valid collection values, which is the main precondition for calling this tool. It does not, however, clarify when to prefer this over sibling hexvero_list or hexvero_export, so the guidance is strong but not exhaustive.

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