get_roll_rc_rate

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

No annotations are provided, so the description must convey behavioral traits. It explains the tool returns a value with unit and type, and mentions legacy interpretation. However, it does not explicitly state that this is a read-only operation or describe side effects.

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 sentence that efficiently communicates key information (unit, legacy mode, type, default). It is appropriately concise, though could be slightly more structured.

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 no output schema, the description partially covers return value semantics (type, unit) but does not specify the exact return structure (e.g., whether it's a raw number or wrapped in JSON). Adequate but not fully complete.

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 tool has no parameters, but the description adds meaning by explaining the returned value's unit, data type (UINT8), and default (7). This goes beyond the schema which has no parameter properties.

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 retrieves the roll_rc_rate parameter, specifying the unit (deg/s×10) and legacy RC multiplier interpretation. It distinguishes from siblings by naming, but lacks explicit differentiation from similar get_*_rc_rate tools.

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 on when to use this tool versus alternatives like set_roll_rc_rate or other getters. The context of flight controller parameter retrieval is implicit but not explicitly described.

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