ppsspp_send_analog

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

Without annotations, the description discloses key behavioral traits: 'Modifies emulator analog input. State persists until updated.' and describes the return string. This is adequate for a simple stateful setter, though rate limits or side effects are not mentioned.

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 sections (PURPOSE, USAGE, BEHAVIOR, RETURNS) and is concise, covering all necessary points without extraneous words. A minor improvement could be removing redundant phrasing.

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 the simple nature of the tool, complete schema coverage, and no output schema, the description fully addresses usage, behavior, and return format. The context of siblings (all emulator commands) is clear, and no further details are needed for an AI agent to use the tool correctly.

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 100% description coverage, but the description adds useful context: it explains the coordinate system with examples like '(0,0) neutral, (1,0) full right, (0,-1) full up' and notes that 'right' is reserved. This goes beyond the schema's min/max and enum descriptions.

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 'Set the PSP analog stick state' and specifies that it handles one of left/right, noting the PSP only has one stick natively. It differentiates from sibling tools like ppsspp_press_button by explaining it is for analog input needed in games.

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 'Drive games that need analog input — character movement, camera control.' It also clarifies that 'right' is reserved for forward-compat, guiding selection between sticks. However, it does not explicitly contrast with digital press tools or state when not to use.

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