write_hex

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't disclose whether the write requires an active session, mutates instruction memory, whether an address is required or defaults to current position, or what happens if the write crosses section boundaries. The only hint is the mnemonic 'wx'.

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?

Very short and front-loaded. The two sentences are efficient, though the parenthetical '(wx)' and the example could be integrated more cleanly. No wasted words, but somewhat terse for the complexity of the operation.

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 mutation tool with three parameters, no annotations, and no explanation of session/address behavior, this is incomplete. The output schema exists, so return values needn't be explained, but the write's effect on memory and required context are missing.

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% for three parameters. The description explains what 'data' should look like (a hex string like '909090'), which is helpful, but says nothing about 'address' (does it default to current position? is it virtual or physical?) or 'session_id' (which session is used if omitted?).

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?

States a specific verb (write) and resource (hex values), and clarifies this is the 'wx' command. An agent can distinguish it from sibling write_assembly and write_nop, though it doesn't explicitly contrast them.

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 versus write_assembly, write_nop, or execute_command. The description gives no context about the scenario (debugging session? patching a binary?) in which hex writing is appropriate.

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