ppsspp_step

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

No annotations provided, so description carries full burden. It discloses that it modifies emulator run state, executes one instruction, returns to stepping mode, and errors if not in stepping mode. Return format is also specified.

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?

Front-loaded with PURPOSE and USAGE sections. Every sentence is valuable; no waste. Extremely concise yet comprehensive.

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?

Covers all necessary context: stepping mechanism, relation to frame-advance, prerequisites, return value. No output schema exists but return is described. Complete for a zero-parameter tool.

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?

No parameters exist, so baseline is 4. The description does not need to add parameter details, and the purpose is fully covered.

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 purpose: stepping the MIPS CPU by one instruction (cpu.stepInto). It uses specific verbs and resources, and distinguishes from sibling tools like ppsspp_resume (frame advance) and ppsspp_pause (enters stepping mode).

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?

Explicit usage guidance: set a breakpoint then step, with clear note that it is not a frame-advance. It also states when to use alternatives (set breakpoint and ppsspp_resume) and prerequisites (emulation must be in stepping mode via ppsspp_pause).

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