dolphin_set_wiimote_angular_velocity

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

Disclosed as 'DESTRUCTIVE to angular-velocity state' with 'ClearOn::NextFrame semantics', giving clear behavioral expectations for a tool with no annotations.

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?

Uses labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS) with minimal, effective sentences. No superfluous content.

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 purpose, usage, behavioral effects, and return format adequately. Lacks error handling or edge cases, but is sufficient for typical use given no output schema.

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?

Input schema already describes each parameter with units. Description repeats units and adds context about axes but does not significantly expand beyond the schema.

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?

Description clearly states 'Set the Wii MotionPlus angular velocity on the given port', specifying the action and resource. It distinguishes from sibling tools like dolphin_set_wiimote_acceleration and dolphin_set_wiimote_pointer.

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?

Provides explicit usage context: 'Use for games that read rotation rate from the MotionPlus add-on' and mentions prerequisite about controller config. Does not explicitly contrast with alternatives but is sufficiently clear.

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