fetch

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

With no annotations, the description carries the full burden. It discloses that no re-execution occurs, rows continue exactly where the last page ended, and the cursor auto-closes when exhausted (has_more=false). This is good coverage for a pagination tool, though it does not address error handling or invalid cursors.

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 sentences with high information density, front-loaded with the purpose. Every sentence adds value, no fluff or redundancy.

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 output schema covers return values, so the description rightly focuses on usage. It covers continuation, no re-execution, and auto-close, which are the key behaviors for a pagination tool. Minor gaps like error cases are acceptable given the tool's simplicity.

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 0%, so the description must compensate for undocumented parameters. It only references 'cursor' implicitly ('open cursor'), but never explains it or mentions 'page_size' at all. The agent gets no help on these parameters beyond their names in the schema.

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 the action ('Fetch the next page'), the resource ('an open cursor'), and implies its role in pagination by referencing 'returned by query' and 'where the last page ended.' It is specific and distinct from siblings like query or close.

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?

It explicitly indicates when to use the tool (when you have a cursor and want the next page) and notes that the cursor auto-closes, so no manual close is needed. It does not explicitly state that query is for the initial fetch, but this is strongly implied by 'returned by query.'

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