page_generate_cursor

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions output characteristics like opaque cursors and relay-style connections, but does not state whether the tool writes files, requires authentication, has side effects, or what the actual generated result looks like. This is a significant gap for a generation tool.

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?

A single, front-loaded sentence with no filler. It conveys the essential purpose and distinguishing characteristics without wasting words.

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?

The schema fully documents parameters, but there are no annotations and no output schema. The description explains what is generated at a high level but does not clarify the output format, side effects, or any behavioral expectations. It is minimally viable but leaves notable gaps for an agent attempting to invoke it 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 description coverage is 100%, so the schema already documents all four parameters. The description adds useful conceptual context about cursors and relay-style connections but does not elaborate on how parameters map to the generated output, which is acceptable given the schema already carries that weight.

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 states a specific verb ('Generate'), a specific resource ('cursor-based pagination'), and two distinguishing characteristics ('opaque cursors' and 'relay-style connections'). This clearly differentiates it from sibling tools like page_generate_offset and page_generate_keyset.

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 implies the tool is for cursor-based pagination, which is a clear context clue. However, it does not explicitly mention when to prefer this over the offset or keyset pagination siblings, nor does it provide any when-not-to-use guidance.

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