read_memory

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

The description explains the basic behavior (reading memory) and parameter meanings. However, it lacks details on side effects, error handling (e.g., invalid address), permissions, or whether the operation is safe. Since no annotations are provided, the description carries the full burden but does not fully address these aspects.

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 and front-loads the purpose. The parameter details are listed in a readable format, though a more structured layout (e.g., bullet points) could improve scannability.

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 existence of an output schema, return values need not be explained. However, the description omits important context for embedded debug, such as alignment requirements, endianness, or address validity. This leaves gaps for correct usage.

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 coverage is 0%, but the description explains each parameter: address as hex, count as number of units, width as bits (8/16/32). This adds valuable meaning beyond the schema's type and default 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 clearly states it reads memory from the target and explains the parameters (address, count, width). However, it does not explicitly differentiate from sibling tools like read_register or read_variable, which also read data but with different contexts.

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 tool versus alternatives, no prerequisites or conditions mentioned. The description is purely functional without usage context.

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