read_more

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

No annotations are provided, so the description carries full burden. It correctly indicates a read operation ('Retrieve'), implying non-destructive behavior. However, it does not disclose details like idempotency, rate limits, or whether the slice is inclusive/exclusive. The minimal disclosure is adequate for a simple retrieval tool.

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 clearly states the action and key concept. It is front-loaded and contains no unnecessary words. Every part earns its place.

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 lack of output schema, zero parameter documentation, and no annotation coverage, the description is too brief. It does not cover return value details, error conditions, or constraints on offset/length. The tool is simple but more context (e.g., default length, max offset) would improve completeness.

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?

The input schema has 0% description coverage, and the tool description does not explain any parameter semantics. It only mentions 'character offsets' without specifying which parameters (offset, length) that applies to. No guidance on defaults, range, or format for any parameter.

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 uses a specific verb ('Retrieve') and resource ('slice of a stored full output') and mentions the key parameter ('handle' and 'character offsets'). It clearly distinguishes from sibling tools like 'invoke_tool' or 'search_tools' which serve different purposes.

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?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description does not mention prerequisites, typical use cases, or when not to use it. The absence of any when-to-use or when-not-to-use guidance limits its helpfulness.

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