dosbox_reset

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

With no annotations, the description must convey behavioral details, but it only states the action. It does not disclose potential data loss, unpredictability, or what happens to the guest state, which is critical for a reset 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 a single, focused sentence with no filler. It communicates the core operation and the key parameter distinction efficiently.

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?

Given the tool's simplicity (one parameter) and the presence of an output schema, the description covers the essential purpose but omits any side-effect warnings or guidance on when to prefer it over state restoration. It is minimally adequate but leaves gaps in behavioral 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 phrase 'optionally without a full machine reset' directly explains the dos_only parameter, adding meaning beyond the bare boolean schema. It tells the agent what false (default) and true likely do, compensating for the 0% schema description coverage.

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 ('Reset') and the resource ('DOS guest'), and distinguishes it from sibling tools like dosbox_pause, dosbox_save_state, and dosbox_capture_screen. The optional modifier hints at two distinct behaviors.

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 implies two usage modes via the dos_only parameter but does not explicitly say when to choose a full machine reset vs. a DOS-only reset, nor does it compare to alternatives like dosbox_load_state or dosbox_break_on_next_exec. There is no guidance on when not to use this tool.

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