Read bounded native cursor pages

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

Adds substantial behavior beyond the annotations: automatic hasNextPage/endCursor inclusion, stopping on repeated or missing cursors, returning continuation state, aborting remaining pages on API errors, and no retries. These are exactly the runtime traits an agent cannot get from readOnlyHint/idempotentHint, so the description earns high marks.

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 dense sentences, front-loaded with the read scope, then pagination guarantees, then error semantics. Every sentence carries distinct information with no filler.

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?

With no output schema, the description properly describes what comes back (hasNextPage/endCursor, continuation state) and how failures are handled. It is nearly complete for a 3-param tool, though it never says where the operation enums come from or how to discover valid query shapes, which the get_operation_schema sibling implies is needed.

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 only 33%, so the description must compensate. It does partially: 'one to five pages' restates the max_pages bound and 'cursor'/'continuation state' gives meaning to the first/after fields buried in the nested arguments object. However, the operation enum values and the overall arguments structure remain unexplained in prose, leaving the compensation incomplete.

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: reading one to five pages of a schema-generated query, with the key distinguishing trait (bounded multi-page cursor reads) up front. It does not name which sibling it replaces (e.g. graphql_query or get_operation_schema) or clarify what a 'schema-generated query' means relative to those tools, so it is clear but not fully differentiated.

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 explicit when-to-use guidance: nothing says when to prefer this over graphql_query, get_operation_schema, or the typed single-item getters (get_posts, get_content_items, etc.). The reader must infer usage from the 'schema-generated query' phrase alone, and no exclusions or prerequisites are stated.

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