desmume_step_instruction

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a 'bounded wait per step' and the instruction count range, but it does not disclose side effects like mutating CPU state, whether the emulator must be paused, whether breakpoints are respected, or what the tool returns after stepping.

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 that captures the core action, range, and a key behavioral trait. Every word earns its place with no unnecessary filler or repetition.

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?

This is a debugging control tool with four parameters (including a nested array) and no output schema or annotations. The description is too sparse to convey essential context such as expected emulator state, return values, what additionalRegions does, or how this step operation interacts with breakpoints and pauses.

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?

Schema description coverage is 0%, so the description must compensate. It implicitly references the 'count' parameter via '1 through 100', but it does not explain captureContext, perStepTimeoutMs, or additionalRegions. The description adds minimal meaning beyond the raw schema.

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 uses a specific verb 'Single-step' with a clear resource ('ARM9 instructions') and a scope ('1 through 100'). It inherently distinguishes from sibling tools like desmume_continue and desmume_pause by describing a controlled, instruction-by-instruction execution.

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 tool name and description imply its use for stepping through ARM9 instructions, but it provides no explicit when-to-use or when-not-to-use guidance, nor does it name alternative tools like desmume_continue. The context is implied rather than clearly stated.

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