set_pitch_rc_rate

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

With no annotations provided, the description carries full burden. It only mentions the value type and default, but does not disclose any side effects, persistence behavior, or prerequisites for setting this parameter (e.g., requiring a connected flight controller).

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 extremely concise, consisting of one sentence plus a bracketed note. It is front-loaded with the essential purpose and type information, with no wasted 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 integer setter with one parameter and no output schema, the description is adequate. However, it could be improved by explicitly stating the allowed range (UINT8 implies 0-255) or any side effects. It meets the minimum viable standard.

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 'Pitch rate at stick center' and 'default: 7' beyond the schema description which only says 'Value for pitch_rc_rate (UINT8)'. This provides meaningful context for the parameter.

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 tool sets 'pitch_rc_rate' and specifies it is 'Pitch rate at stick center'. This verb+resource formulation is specific and distinguishes it from siblings like set_roll_rc_rate and set_yaw_rc_rate.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., set_roll_rc_rate), nor does it mention any prerequisites or restrictions.

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