set_roll_expo

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 explains the effect on stick response but does not disclose side effects, persistence, or whether a reboot/save is required. The type and default are given, but the schema's min/max conflict with the implied UINT8 range.

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 two sentences plus a parenthetical note, all front-loaded with the action. Every word serves a purpose, with no redundancy or unnecessary elaboration.

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?

The description covers the basic meaning and default, but is incomplete regarding the value range (schema allows large integers but description implies 0-255 UINT8). It also lacks info on persistence or interaction with other settings. Given no output schema, the description should clarify these points.

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 schema description is minimal ('Value for roll_expo (UINT8)'). The tool description adds significant meaning by explaining the exponential curve behavior and the effect of higher values. This provides useful semantic context 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 'Set roll_expo' and explains the parameter's effect: 'transition between center sensitivity and max rate. Higher = more expo, slower center, faster edges.' It distinguishes from sibling expo tools (pitch, yaw, thr) by specifying 'roll'.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, it lacks context about prerequisites or when adjustment is appropriate (e.g., during tuning, while disarmed).

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