ppsspp_resume

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

Discloses that it modifies emulator run state and is idempotent (resuming already-running is a no-op). No annotations present, so description fully covers expected behavior.

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?

Very concise with clear labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Front-loaded and no wasted words.

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 zero-parameter tool with no output schema, the description covers purpose, usage, behavior, and return value fully. No gaps.

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 in input schema (0 params, 100% coverage). Description does not need to add parameter info; baseline 4 applies.

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?

Explicitly states 'Resume PSP emulation from a paused/stepping state' with a specific verb and resource. Clearly distinguishes from sibling tools ppsspp_pause and ppsspp_step.

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?

Describes itself as counterpart to ppsspp_pause and specifies use after a paused inspection sequence. Also points to alternative tool ppsspp_step for single frame stepping.

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