gangtise_read_response

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

With no annotations provided, the description carries the full burden. It discloses that the tool only reads files with a specific prefix, in a temporary directory, generated by the same process. It also explains the chunked reading mechanism. It does not cover error scenarios or return format, but for a read-only utility, this is adequate.

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 three sentences long, front-loading the purpose and then adding usage conditions. Every sentence is necessary and clear. 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?

The description covers purpose, usage conditions, and basic constraints. However, it does not mention the return format or error handling. Given the tool's nature (reading truncated data), a hint about output structure would improve completeness. Still, it's fairly complete for a utility tool.

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% with good descriptions for all three parameters. The description adds value by explaining that 'saved_to' comes from other tools' '_saved_to' field, which clarifies its origin. Offset and limit are standard and their schema descriptions are sufficient.

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 tool's purpose: reading truncated large responses from other tools. It specifies the triggering condition (when truncated: true and _saved_to field present) and the method (chunked reads by offset/limit). This distinguishes it from sibling tools, which are all data-fetching tools.

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 explicitly states when to use the tool: when other tools return truncated responses with a _saved_to path. It also restricts usage to files with the gangtise-mcp- prefix in the system temp directory. No alternatives are needed as no sibling tools serve this purpose.

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