set_roll_srate

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

Without annotations, the description must disclose behavioral traits. It only states the purpose and default but does not mention side effects (e.g., if the change persists, requires reboot, or affects flight behavior). The description implies a write operation but lacks detail.

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 noun phrase with parenthetical details. Every word is functional and front-loaded with the key information. No redundancy or unnecessary text.

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 with one parameter and no output schema, the description covers purpose, type, and default. It does not mention persistence or scope (e.g., per profile), but the 'ACTUAL system' hint suggests it affects the running system. Overall, sufficient but could add a note about when changes take effect.

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%, but the description adds meaning beyond the schema by defining 'roll_srate' and specifying the default value (67) and data type (UINT8). The schema only labels it as 'Value for roll_srate', so the description adds significant context.

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', the resource 'roll_srate', and explains what the parameter controls: 'Roll super rate — max rate at full stick deflection (ACTUAL system)'. This distinguishes it from sibling tools like set_pitch_srate or set_yaw_srate.

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 provides no guidance on when to use this tool versus alternatives. It does not mention preconditions, recommended scenarios, or when not to use it. For a field-specific setter, this is a significant gap.

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