get_gyro_cal_on_first_arm

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

With no annotations, the description carries full burden for behavioral disclosure. It claims 'recalibrates gyro' which conflicts with the 'get' naming, and does not clarify whether the tool reads a setting or performs an action. The note '[UINT8, default: OFF]' hints at a parameter reading but is ambiguous.

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 short but wastes the first sentence by repeating the tool name. The remaining sentences are functional but could be better structured to avoid redundancy.

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?

Without an output schema, the description should clarify what the tool returns. '[UINT8, default: OFF]' hints at the return type but is vague. The tool's overall purpose (read vs. write) is not clearly defined, leaving the agent with incomplete information.

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 zero parameters and schema coverage is 100%, so the description does not need to explain input semantics. However, the included '[UINT8, default: OFF]' is contextually useful but could be misinterpreted as a parameter description.

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 states 'Recalibrates gyro on first arm' which implies a write action, but the tool name is 'get_gyro_cal_on_first_arm', suggesting a read operation. This contradiction makes the purpose unclear.

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 says 'Useful if the FC warms up and gyro drifts before the first arm,' providing a specific use case. However, it does not mention when to avoid using the tool or suggest alternatives from the extensive sibling list.

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