set_spa_pitch_mode

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

No annotations are provided, so the description must disclose behavioral traits. It only states that the tool sets a value (a mutation), but does not mention side effects, persistence, or any other runtime behavior. Minimal transparency.

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 a single, compact sentence with supplementary details in parentheses. Every element serves a purpose; no fluff.

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?

For a simple one-parameter tool, the description covers the core function and a key prerequisite. However, it does not specify valid values for the parameter (e.g., 'ON', 'OFF', etc.) nor describe the return value. It is adequate but could be more complete.

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 one parameter with a description that reads 'Value for spa_pitch_mode (UINT8)'. The tool description adds extra info: default value ('OFF (per profile)') and data type, which aids understanding 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?

The description clearly states the tool sets 'spa_pitch_mode' for pitch SPA mode. It is distinct from the corresponding get tool and other set tools via the specific parameter name. However, it lacks explicit differentiation from other set tools beyond naming.

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 notes a requirement: 'Requires: USE_WING', providing a precondition for using the tool. No guidance on when not to use it or alternatives is given, leaving room for improvement.

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