set_roll_rc_rate

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

No annotations are provided, so the description bears full responsibility for behavioral traits. It states the tool sets a configuration value, implying mutation, but does not disclose side effects (e.g., whether changes persist, require reboot, or need disarming). The description is adequate but lacks important behavioral context.

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, well-structured sentence that front-loads the tool name and action. It includes essential context (unit/legacy mode, default) without any extraneous words. Every part is informative.

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 (one parameter, no output schema), the description is largely complete. It explains the parameter's meaning and default. However, it lacks information about the effect of the set operation (e.g., immediate vs. saved after reboot), which would improve completeness for a configuration tool.

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 value by explaining that the value represents the actual roll rate in deg/s×10 or a legacy RC multiplier, with a default of 7. This interpretation goes beyond the schema's 'UINT8' type, aiding the agent in selecting an appropriate numeric value.

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 identifies the tool as setting the roll_rc_rate, specifying it as the roll rate at stick center. It distinguishes from siblings like set_pitch_rc_rate and set_yaw_rc_rate by naming the axis. The note about ACTUAL vs legacy modes further clarifies the parameter's interpretation.

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 (e.g., set_roll_rate_limit for max rate, set_roll_srate for super rate). No context is given for prerequisites or circumstances where this should or should not be used.

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