read_offloaded_response

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

With no annotations, the description must carry the behavioral disclosure burden. It correctly states the tool reads a single bounded chunk rather than the entire response, and it references the offload summary as the source of context. However, it does not describe behavior for invalid or out-of-range chunk_index values, chunk stability, or error cases. It also mentions 'total_chunks' as if it were an input, though it is not present in the schema, which could slightly mislead.

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 exactly two sentences, with the primary action front-loaded and no redundant wording. Every sentence contributes either the purpose or the input-sourcing guidance, making it efficient and easy to scan.

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 two-parameter tool, the core purpose and input provenance are clear. However, because there is no output schema, the description should explain the response shape and iteration logic more explicitly — for example, that chunk_index ranges over 0..total_chunks-1 — which is only implied. This is a meaningful gap for an agent that needs to read all chunks reliably.

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 100%: both parameters already have descriptive text ('worksection://offload/... URI' and 'Zero-based chunk to read'). The description adds context by pointing to the offload summary, but the referenced 'total_chunks' is not a declared parameter, so the added value is limited. This matches the baseline for fully documented schemas.

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 identifies a specific verb ('Read') and a precise resource ('one bounded chunk of a response that was too large to return inline'). This clearly distinguishes it from sibling getter tools, which target domain objects rather than offloaded response chunks. It also names the input source ('offload summary'), leaving no ambiguity about what the tool does.

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 instruction to 'Use the resource_uri and total_chunks from the offload summary' provides a clear context for when this tool is appropriate, and implies it should be used when consuming a previously offloaded large response. It does not explicitly state exclusions or alternatives, but no sibling tool covers the same offload-read purpose, so the guidance is sufficient.

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