get_buffer_contents

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the read-only nature ('Read'), the base64 encoding of returned data, and that metadata accompanies the data. However, it does not explain error behavior for invalid resource IDs, the impact of out-of-range offsets, or any side effects (which are likely none given the read-only nature). The disclosure of base64 encoding is useful and beyond what the schema reveals.

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 efficiently structured with a single purpose sentence followed by a compact parameter list and a one-line return specification. It is appropriately sized for a simple read operation with three parameters. No filler or redundant content, though the return format could have been included in the parameter section for tighter structure.

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 this is a relatively simple read operation, the description covers the necessary usage context: what it reads, how to configure reads (offset/length), and what comes back (base64 + metadata). The output schema exists, so return format details beyond base64 encoding are handled elsewhere. The only minor gap is explicit usage guidance versus sibling tools, but the overall definition is functionally complete for an agent to call it correctly.

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 is fully responsible for parameter semantics. It explains 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, 0 for entire buffer'. These definitions add meaningful context beyond the bare schema types and defaults, particularly the semantic meaning of the default 0 values.

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 states a clear verb ('Read') and resource ('buffer resource'), and provides enough detail to distinguish it from siblings like get_texture_data (which reads textures) and get_draw_calls (which reads draw call lists). It does not explicitly differentiate from get_texture_info, but the buffer-specific focus is clear enough for an agent to identify the resource type it operates on.

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 context through the 'read' framing and buffer resource specification, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. An agent might reasonably infer that this reads raw buffer data while get_texture_data handles textures, but this is left to inference rather than stated.

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