read_bytes

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

The word 'Read' implies a pure, side-effect-free operation, yet the annotation declares readOnlyHint=false, and the schema's analysis_project_id shows results may be persisted into an investigation. The description never reconciles this, nor does it describe the return encoding (raw bytes, hex, base64) or truncation behavior at the 256-byte default.

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 front-loaded sentence with no filler. Its brevity is efficient, though it leaves too much implicit for a 4-parameter tool.

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?

No output schema and 4 params with sparse descriptions mean the description has to carry more weight. It should say what a successful response looks like (byte payload format) and clarify the two address syntaxes; instead it stops at restating the tool's core action.

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 only 25%: only analysis_project_id is documented. The description adds nothing about the required address format — which the regex shows can be a hex offset OR a module:offset qualified form — nor about the length cap or what the nullable document parameter does.

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?

Specific verb+resource: 'Read bytes at an address in the active ELF analysis image' tells an agent exactly what data comes back and what context it lives in. It does not differentiate from nearby siblings such as read_function_instructions or procedure_assembly, which read overlapping content.

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 gives no when-to-use guidance and names no alternative, despite dozens of siblings that also return binary content (read_function_instructions, search_strings, read_evidence). 'Active ELF analysis image' only faintly implies a binary session must be open; that prerequisite is never stated.

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