write_memory

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

No annotations are provided, so the description carries the full burden. It discloses address and value formats (hex/decimal) and word_size options, but does not mention side effects, permission requirements, or whether memory is volatile/non-volatile. Adequate for a basic write operation.

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 with 5 lines, including clear parameter annotations in docstring style. Every sentence adds value, no redundant information, and the purpose is front-loaded.

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 parameters with no enums, an output schema (though not shown), and no nested objects. The description adequately explains the parameters and purpose. Minor gap: does not mention that writing occurs on the target device memory, but this is implied by context.

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?

The description adds significant meaning beyond the input schema: it specifies that address and value can be hex (0x...) or decimal, and explains word_size as transfer size in bits with allowed values (8, 16, 32). Schema description coverage is 0%, so the description compensates well.

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 clearly states 'Write a single value to memory' with a specific verb and resource. It distinguishes from sibling tools like read_memory and write_core_register by specifying 'single value' and the memory context.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies usage via the verb 'write', but does not mention alternatives like block writes (though no write_memory_block sibling exists). The context from sibling names partially compensates.

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