ppsspp_ping

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

The description details that the tool has no side effects, calls the 'version' event, and times out after ~10 seconds under conditions like PPSSPP not running or remote debugger disabled. It also mentions the prerequisite 'Allow remote debugger' setting. With no annotations provided, this fully informs the agent of behavioral traits.

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 structured with clear labels (PURPOSE, USAGE, BEHAVIOR, RETURNS), is very concise, and front-loads the essential information. Every sentence adds value without redundancy.

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 output schema, the description adequately explains the return format. It covers purpose, usage, behavior (including timeout), prerequisites, and return value. With 0 parameters, no further detail is needed; the description is complete for this tool's simplicity.

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 0 parameters, so schema_description_coverage is 100%. The description adds value by explaining what the tool returns ('Single line 'pong (PPSSPP VERSION)''), exceeding the baseline expectation for zero-parameter tools.

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 tool's purpose: 'Verify that the PPSSPP WebSocket debugger is reachable and responding.' This is a specific verb and resource, and it distinguishes the tool from sibling tools like ppsspp_get_info or ppsspp_breakpoint_add, which serve different purposes.

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 'Call once at start-of-session before any other tool calls; if it succeeds, the WebSocket handshake worked.' This provides clear guidance on when to use the tool and what the result implies.

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