dosbox_write_memory

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

Even though annotations already signal a destructive, non-read-only operation, the description adds valuable behavioral detail: writes land in the running game, are not undoable, and the game may recompute a field shortly after it is written. This is exactly the kind of non-obvious runtime behavior an agent needs to know. No contradiction with annotations.

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?

Three sentences deliver the core purpose, a motivating use case, and the critical timing/durability caveat. There is no filler or repetition; every sentence earns its place.

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 destructive memory-mutation tool, the description is nearly complete: it says why to use it, what makes it dangerous, and what timing to respect. It does not explicitly state the requirement that a target session/game is already attached or running, nor mention targeting via pid. That is a minor gap and is mostly inferable from sibling tools and the schema.

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 nested schema already explains offset, size, value, and hex well, but the description adds little parameter-specific detail beyond casting writes as patches to game state. It does not clarify the top-level pid, writes, or segment semantics in prose, and top-level schema description coverage is only 33%. The description is behaviorally useful but does not fully compensate for that gap.

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 opens with a specific verb and target: 'Patch the game's data segment.' It then clarifies the concrete use case—setting up a state like a treasury, rank, or flag to reach a particular screen or code path. This clearly distinguishes it from the sibling read/search/memory tools.

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?

It gives clear context for when the tool should be used: when a state would otherwise take hours of gameplay. It also gives timing guidance: patch where the value will be read before the game recomputes it. It does not explicitly state when-not-to-use or name alternatives, so it stops just short of perfect.

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