get_spa_yaw_mode

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

No annotations are provided, so the description carries the full burden. It specifies the data type (UINT8), default (OFF per profile), and a prerequisite (USE_WING). However, it does not disclose that the tool is read-only (implied by 'get'), nor describe the return value format or any side effects. Basic behavioral context is present but could be more explicit.

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 extremely concise: one sentence plus a requirement annotation and type/default info. Every element is functional and to the point, with no wasted words. Front-loaded with the key purpose.

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 tool's simplicity (no parameters, no output schema), the description provides adequate context: type, default, and prerequisite. It could explicitly state that it retrieves the current setting value of SPA yaw mode per profile, but overall it is complete for its complexity level.

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 tool has no parameters, and schema coverage is 100% (empty schema). The description adds value by specifying the type, default, and prerequisite, which are not in the schema. It compensates for the lack of parameter documentation.

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 it retrieves the SPA mode for yaw. The tool name and description together differentiate it from sibling tools like get_spa_pitch_mode and get_spa_roll_mode by specifying the axis. No explicit mention of alternatives, but name and context make it clear.

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 notes the requirement `USE_WING` for this tool to be valid, and provides the type (UINT8) and default value (OFF per profile). It implies use when you want to read the current yaw SPA setting, but does not explicitly state when not to use it or list alternatives (e.g., use set_spa_yaw_mode to change).

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