set_failsafe_throttle

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

With no annotations, the description carries full burden. It discloses the dual-role behavior in failsafe stages, the default meaning, and the critical consequence for GPS Rescue if set incorrectly. This is good transparency for a numeric setter.

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?

Three compact sentences. First defines purpose and scope, second gives default, third adds critical consequence. No redundancy, well front-loaded, every sentence earns its place.

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 setter with one parameter, the description explains the throttle's role in failsafe stages and GPS Rescue. Missing output schema is acceptable for a setter. Provides sufficient completeness given the tool's simplicity and lack of annotations.

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?

Schema coverage is 100% but description adds value beyond schema by specifying default (1000) and contextual meaning (motors off, hover throttle for GPS Rescue). The schema already indicates UINT16, so description complements rather than replaces.

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 the failsafe_throttle value, specifies where it applies (Landing Mode Stage 2 and Stage 1 fallback), and provides critical context (default, GPS Rescue). It distinguishes itself from many sibling set_ tools by its specific resource and behavior.

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 gives context on when the throttle is applied and a crucial GPS Rescue requirement, but does not explicitly state when to use this tool versus alternatives like other failsafe settings or get_failsafe_throttle. No when-not guidance is provided.

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