bizhawk_pause

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

No annotations provided, so description carries full burden. It discloses: modifies emulator run state, Lua bridge keeps polling, other calls still work, returns error if core doesn't expose pause, and no-op if already paused. This is comprehensive.

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 well-structured with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Every sentence adds value; no fluff. It is both concise and informative.

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 no parameters, no output schema, and the tool's simplicity, the description is complete. It covers purpose, usage, behavior, error handling, and return value, and references sibling tools and capabilities check.

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 input schema has no parameters (0 params, 100% coverage). Baseline for 0 params is 4. The description adds no parameter info because none needed, but it does add context about behavior and usage.

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: 'Pause emulation — freeze game-logic clocks and hold the current frame on screen.' It uses a specific verb and resource, and distinguishes itself from siblings like bizhawk_unpause and bizhawk_frame_advance.

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 description explicitly says when to use: 'Use before a sequence of memory-inspect / write / screenshot calls when you need a stable game state across calls.' It also provides alternatives: 'Use bizhawk_unpause to resume; use bizhawk_frame_advance to step single frames without leaving pause.'

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