sql_statements_get_result_chunk

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

Annotations already declare readOnlyHint=true. The description adds context about EXTERNAL_LINKS results but does not disclose behavior like error handling for invalid chunk_index or whether chunks are limited.

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?

The description is a single sentence that is front-loaded with the action and resource. It is concise with no wasted 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?

Given the tool's simplicity with two parameters and an output schema, the description is adequate but lacks mention of the need to first execute a statement and what EXTERNAL_LINKS means in terms of result chunking.

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?

Both parameters have clear descriptions in the schema ('Statement ID', 'Zero-based chunk index'). The description adds no additional meaning beyond what the schema already provides.

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 specifies the action 'Fetch' and the resource 'a single chunk of an EXTERNAL_LINKS result'. It distinguishes from sibling tools like sql_statements_get and sql_statements_execute by narrowing to chunked results.

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 usage for chunked results but does not explicitly state when to use this tool vs alternatives (e.g., sql_statements_get for full results) or any prerequisites (e.g., executing a statement first).

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