set_iterm_rotation

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

No annotations are provided, so the description carries full burden. It mentions rotation behavior and effect, but fails to clarify the actual parameter type (UINT8 vs string in schema), valid range, or side effects like need for reboot. This is insufficient for a mutation tool.

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, front-loaded sentence followed by a contextual note and type/default hint. No extraneous words.

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 setter, the description covers purpose and a use case. However, it misses important context about parameter values (range, format) and how it interacts with other I-term settings. The lack of output schema is noted but not compensated.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning about the parameter beyond the schema's 'Value for iterm_rotation (UINT8)'. It does not explain what values are valid or how to format them.

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 action: 'Rotates I-term vector with the aircraft during yaw to reduce cross-axis coupling.' This distinguishes it from other I-term-related tools like set_iterm_relax or set_iterm_windup. The note about 3D flying further clarifies its specific use case.

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 'Primarily useful for 3D flying,' giving a hint about when to use. However, it does not explicitly state when not to use or contrast with alternatives like set_iterm_relax. More explicit guidance would help.

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