debug_write_memory

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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It states that the tool writes to debugged process memory, but it does not warn that this is destructive to the target process state, can crash the debuggee, or requires the debug session to be alive. The mutating and potentially harmful nature of the operation is under-communicated.

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, efficient sentence with no redundant wording. It is front-loaded with the core action and resource, but it sacrifices important behavioral clarity for brevity.

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 tool that mutates process memory and has no output schema or annotations, this description is incomplete. It does not mention whether the write is immediate, whether it can corrupt execution, what the return value is, or that an active session is mandatory—all relevant for safe invocation by an agent.

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%, so every parameter is already documented in the input schema. The description's mention of 'hex bytes or a string' mirrors the `hex_bytes` and `data`/`as_string` parameters but adds no extra semantic detail, such as how `hex_bytes` and `data` interact or what happens when both are provided.

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 states a clear action ('Write memory in the debugged process at a specific address') and identifies the two data modes ('hex bytes or a string'). It is specific enough to understand the operation, though it does not explicitly distinguish this from the sibling `write_bytes` tool, which could also be interpreted as writing bytes somewhere.

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 is given about when to use this tool versus alternatives like `write_bytes` or `debug_read_memory`. The description does not mention prerequisites such as an active debug session or caution about using it only when intentional memory modification is required.

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