ida_read_bytes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the read operation and output format, implying a non-destructive read, but does not mention failure modes (e.g., invalid address), endianness, or any prerequisite such as IDA being active. Basic transparency is present, but richer context is missing.

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, clear, and concise sentence that packs the essential purpose ('read raw bytes') and output ('hex+ASCII dump') without any 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?

For a simple two-parameter read tool, the description is largely sufficient: it names the action, the address parameter, and the output format. It does not explain how size is limited or what happens on invalid input, but given the low complexity, it is nearly complete.

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 100%, with both 'address' and 'size' described. The description adds no extra semantic detail beyond the schema, such as how size interacts with output or default behavior. Baseline 3 applies because the schema already documents the parameters adequately.

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 action ('Read raw bytes at an address') and the output format ('hex+ASCII dump'). It distinguishes itself from siblings like ida_disassemble (which decodes instructions) and ida_decompile (which produces pseudocode) by focusing specifically on raw byte reads.

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 its usage (reading raw memory content) but does not explicitly state when to prefer it over alternatives such as ida_disassemble or windbg_read_memory. There are no exclusions or alternative tool mentions, so guidance is only implicit through the tool name and description.

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