disk_read

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

With no annotations, the description carries the full burden. It does disclose the return shape (hex dump or text) and that the offset is absolute, but says nothing about safety/read-only status, behavior on out-of-range offsets, partial reads, or default length of 512.

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?

A single short clause with no wasted words and the key notion (raw bytes at absolute offset) front-loaded, but the brevity comes at the cost of under-specification rather than efficiency.

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 4-parameter, no-annotation, no-output-schema read tool, the description is too thin: it lacks first-call prerequisites, default length behavior, and disambiguation from sibling read/block_read tools.

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% for 4 parameters. The description clarifies 'offset' as absolute and hints at 'as_text' via 'hex dump or text', but leaves 'image' and the 'length' parameter (default 512) entirely unexplained, so it only partially compensates.

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 fragment 'Raw bytes at an absolute byte offset in the image' implies a read operation and names the resource (raw image bytes), but omits the verb and offers no contrast with siblings such as block_read or read, which an agent could easily confuse it with.

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 on when to use this versus block_read, read, strings, or extract; the only implied usage cue is 'absolute byte offset', with no when-not conditions or prerequisites (e.g., image must be opened first).

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