get_buffer_contents

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

The description explicitly states this is a read operation ('Read the contents'), implying non-destructive behavior. However, with no annotations, it does not disclose potential side effects, error handling, or constraints like buffer size limits or required resource state.

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 concise with three sentences and an Args section. It is well-structured, front-loaded with the purpose, and every sentence adds value without redundancy.

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 3 parameters and presence of an output schema (assumed to explain return details), the description adequately covers the tool's behavior. It explains parameters and notes the return format. Could be improved by mentioning error cases or performance implications, but overall complete for a read operation.

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 description coverage is 0%, so the description compensates fully. It defines all three parameters: resource_id as 'The resource ID of the buffer to read', offset as 'Byte offset to start reading from', and length as 'Number of bytes to read', including default values. This adds crucial meaning beyond the schema's type-only definitions.

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 'Read the contents of a buffer resource' with a specific verb and resource type. It distinguishes from sibling tools like get_texture_data by focusing on buffers, and explicitly mentions the return format (base64-encoded bytes with metadata).

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 guidance is provided on when to use this tool versus alternatives. Sibling tools like get_texture_data or get_draw_calls exist, but the description does not differentiate use cases or mention any preconditions.

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