set_gyro_cal_on_first_arm

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

No annotations are provided. The description implies enabling a setting that triggers recalibration on first arm, but it does not disclose behavioral details such as persistence across reboots, side effects, or if it overrides existing calibration. Minimal transparency beyond the basic action.

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?

Extremely concise: two sentences and a type/default hint. Every part adds information without repetition. Perfectly efficient for a simple configuration parameter.

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, the description leaves gaps. It does not specify what the UINT8 values represent (e.g., 0=OFF, 1=ON) or the effect on flight behavior. Without these details, an agent may not know valid inputs or consequences.

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 input schema has 100% coverage with a generic description. The description adds the default value ('OFF') and specifies the data type ('UINT8'), which adds minor value. However, it does not explain acceptable values (e.g., 0 or 1) or their meaning.

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 action ('Recalibrates gyro on first arm') and the resource ('gyro'). It differentiates from sibling 'set' tools by specifying when the recalibration occurs (after power-up on first arm). However, it doesn't explicitly distinguish from other gyro calibration tools like 'set_gyro_calib_duration'.

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?

Provides a specific use case ('if the FC warms up and gyro drifts before the first arm'), which indicates when to use. However, it does not specify when not to use, nor does it mention alternative tools or conditions.

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