set_spa_yaw_mode

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

No annotations are provided, so the description must bear the full burden. It states it's a set operation with a requirement, but does not disclose side effects, persistence, or safety implications. Additionally, there is a type inconsistency: the description says '[UINT8]' while the input schema specifies 'type: string' for the value parameter, which can cause misinterpretation.

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 very short—one line plus a parenthetical note—with no wasted words. It conveys key information efficiently, though it could be better structured (e.g., separating requirements and defaults).

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 simplicity of the tool (one parameter, no output schema), the description covers the basics but lacks context about what SPA mode is, what valid UINT8 values (e.g., ON/OFF or numbers) are, and how this setting affects yaw behavior. Sibling tools in the same domain don't clarify usage.

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?

Schema description coverage is 100% (the only parameter 'value' has a description). The tool description adds the default value and type hint, but adds little beyond the schema's description. Baseline 3 is appropriate.

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 verb 'Set' and resource 'spa_yaw_mode', and explains it's for yaw SPA mode. The requirements and default are noted. However, it doesn't differentiate from sibling tools like set_spa_pitch_mode or set_spa_roll_mode, though the tool name already specifies the axis.

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 mentions the prerequisite 'USE_WING' feature and the default value, giving some usage context. But it lacks guidance on when to choose this tool over alternatives (e.g., get_spa_yaw_mode, set_spa_yaw_center) or when not to use it.

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