memory.write

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Write bytes (hex) to the view'—a mutation action with no mention of side effects, idempotency, error conditions (e.g., invalid address, read-only view), or if data overwrites or appends. This is insufficient for a tool modifying state.

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 sentence with 6 words—very concise. It front-loads the action ('Write bytes (hex)'). However, it sacrifices essential detail for brevity, borderline under-specification.

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?

The tool has 3 required parameters with 0% schema coverage, no annotations, no output schema, and 100+ sibling tools. For a mutating tool in a complex environment (Binary Ninja), the description completely fails to explain addresses, output, or integration with sessions—far from complete.

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 must explain parameters. It mentions 'hex' for data_hex and implies address is a location, but doesn't clarify address format (integer vs string meaning), session_id purpose, or data_hex constraints (length, endianness, partial vs full overwrite). This leaves the agent guessing.

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 title 'memory.write' and description 'Write bytes (hex) to the view' make it clear the tool writes data to a memory view using a specific resource (the view). The sibling list includes 'memory.read', 'memory.insert', and 'memory.remove', which are distinct in operation (read, insert, remove) so this tool's write purpose is well-differentiated.

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 provides no guidance on when to use this tool versus alternatives like 'memory.insert' or 'memory.reader_read'/'memory.writer_write'. Given the sibling tools and context signals (3 required params, 0% schema coverage), the agent has no hints about prerequisites (e.g., an open session with a writable view) or scenarios where writing hex data is appropriate.

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