Continue paged query

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds valuable context about the snapshot TTL (HANA_QUERY_SNAPSHOT_TTL_MS) and the requirement to reuse the same SQL and parameters, which are beyond the structured annotations.

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 that states the purpose and key constraint (same SQL/params, TTL). Every word earns its place; no redundancy or 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?

For a simple pagination tool with a rich schema and output schema, the description covers the essential context: what triggers a truncated result, how to fetch the next page, and the TTL caveat. It might optionally mention the behavior on TTL expiry or that offset should come from the previous result, but the schema already hints at this.

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?

Input schema description coverage is 100%, so the baseline is 3. The description reinforces that snapshot_id comes from a previous result and that offset is typically the prior nextOffset, but these are already partially captured in the schema (e.g., 'usually prior nextOffset'). No extra enrichment beyond schema descriptions.

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') and the specific resource ('a truncated SELECT using snapshotId from a previous hana_execute_query result'). It distinguishes this tool from siblings by focusing on pagination continuation, not initial query execution.

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 when to use the tool: after receiving a truncated result from hana_execute_query with a snapshotId. It doesn't explicitly mention alternatives, but the context is unambiguous. A minor improvement would be stating 'use this instead of re-running the query'.

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