write_memory

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the operation (write) and return (confirmation of bytes written), but it does not disclose potential side effects, prerequisites (e.g., target halted, address validity), or warnings about destructive writes. This is insufficient for a mutation tool.

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: a single-line purpose, followed by a structured list of parameters and return. Every sentence is necessary, and there is no extraneous text.

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 tool has 4 parameters (2 required) and no annotations, the description provides purpose, parameters, and return but lacks prerequisites, error conditions, or usage context (e.g., when the target must be in a specific state). It is adequate but not complete for a write operation with safety implications.

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's Args section adds significant value by explaining that address can be a hex string or symbol name, data must be a hex string of bytes, width defaults to 32 bits, and access is a class prefix. This is clear and goes beyond the schema's type-only definitions, though some constraints (e.g., data length, width power-of-2) are not detailed.

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 explicitly states 'Write data to target memory at a given address,' which is a specific verb+resource combination. It clearly distinguishes itself from sibling tools like 'read_memory' (read) and 'write_register' (register vs memory).

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 that the tool should be used when writing to memory, but it does not explicitly state when to use it versus alternatives (e.g., write_register or write_variable). No exclusions or context are provided, making the guidance implicit rather than explicit.

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