pin_write_mem

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. For a memory-mutation tool it says nothing about required target state (paused vs running), whether writes to code/read-only regions are permitted, reversibility, or what the call 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?

A single short sentence with no filler; the verb and object are front-loaded. It is efficient, though its brevity reflects under-specification rather than deliberate concision.

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 state-mutating tool with no annotations, no output schema, and one undocumented parameter, the description is too thin. An agent cannot tell what 'ea' means, what preconditions apply, or how failures/partial writes are reported.

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?

Only the 'hex' parameter is documented in the schema (with format and example); 'ea' has no description anywhere. With 50% schema coverage, the description needed to compensate by explaining that 'ea' is the target effective address and clarifying hex encoding on the wire, but it adds nothing beyond the name.

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 bytes to target memory'), which clearly separates it from the sibling pin_read_mem. It does not, however, name or differentiate against other siblings or clarify scope beyond the literal operation.

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?

There is no guidance on when to use this versus pin_read_mem or the other pin_* tools, and no stated prerequisites such as whether the target must be paused before writing. The agent is left to infer the context entirely.

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