set_yaw_srate

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

The description only notes the action (set) and provides data type/default, but lacks information on side effects, persistence, required privileges, or whether changes require a reboot. No annotations are present to fill the gap.

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 very short and front-loaded, but it omits essential behavioral details. Conciseness at the cost of completeness reduces overall utility.

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 lack of annotations and output schema, and the presence of many similar siblings, the description is insufficient. It does not explain the tool's role in flight controller configuration or its effects.

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 description adds the data type (UINT8) and default value (67) beyond the schema's generic 'Value for yaw_srate (UINT8)' description. The schema's min/max range is unrealistic, so the description's type hint is more accurate.

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 yaw_srate: Yaw super rate,' indicating the tool sets a specific rate parameter. However, it does not differentiate from other set_ siblings like set_roll_srate or set_pitch_srate, leaving ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_yaw_srate for reading or other set_ tools for different axes. The agent is left without context for appropriate usage.

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