stm32_write_memory

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the write is 'directly' to memory, implying low-level access, but does not warn about potential destructive overwrites, invalid address crashes, or required connection state, which are critical for a memory-write tool.

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, front-loaded sentence with no filler words. It efficiently communicates the core function in ten words.

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 a simple 3-parameter schema with 100% coverage and no output schema, so the description need not explain return values. However, it omits important contextual safety information about the consequences of direct memory writes, making it only minimally 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?

The input schema provides complete descriptions for all three parameters, including address format and data/file payload. The description's 'value or file payload' adds no substantive meaning beyond the schema's own documentation, so this is baseline.

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 the action ('Write value or file payload') and the target ('memory address or peripheral register'), using a specific verb and resource. It distinguishes from sibling tools like stm32_read_memory, stm32_erase_memory, and stm32_flash_firmware by focusing on direct memory/register writes.

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 does not provide any guidance on when to use this tool versus alternatives like flash_firmware or write_option_bytes. No exclusions or prerequisites are mentioned, leaving the user to infer usage from the tool name alone.

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