rzil_set_memory

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

With no annotations, the description must carry the behavioral burden. It discloses the mutation effect and the session precondition, but it does not say what happens on an invalid/expired session, whether the write overwrites existing bytes, or what the tool returns.

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, tight sentence with the action front-loaded and the requirement appended. Every word earns its place and there is no filler or repetition beyond the schema.

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 description covers the core purpose and the key precondition, and the schema covers all parameters. However, with no output schema or annotations, it omits return/error behavior and how this write relates to later rzil_get_memory or rzil_step calls.

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 the baseline is 3. The description adds little beyond the schema, only restating that data is written to an address and that a session is required; both facts are already in the parameter descriptions.

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 specific verb and resource: 'Write data to the Rizin RzIL emulated memory space at a given address.' It clearly differentiates this from sibling tools like rzil_set_register and debug_write_memory by naming the emulated memory domain.

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 gives an explicit prerequisite: 'Requires a persistent session from rzil_init,' which tells an agent this tool cannot be used standalone. It does not explicitly name alternatives or when-not-to-use cases, but the emulated-memory context distinguishes it from debug memory write tools.

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