set_gps_rescue_allow_arming_without_fix

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

No annotations are provided, so the description bears full burden. It discloses the key behavioral effect (arming allowed without fix) and a visible consequence (OSD shows 'RESCUE OFF'), plus the data type and default. It lacks persistence or reboot requirements, but the main behavior is well covered.

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: two sentences plus a bracketed note. Every sentence adds value by stating the function, the consequence, and the parameter format. No extraneous 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 single-parameter setter, the description covers purpose, behavior, and parameter details. However, it omits whether the setting is persistent or requires a reboot, and does not describe the return value (likely success/failure). Given no output schema, these are minor gaps.

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 description coverage is 100% with a generic schema description. The description adds value by specifying the default value ('OFF'), the type (UINT8), and the behavioral context (effect on arming and GPS rescue). This goes beyond the schema's minimal 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 clearly states the verb 'Set' and the resource 'gps_rescue_allow_arming_without_fix'. It explains the purpose: allow arming without a GPS fix, and notes the consequence that GPS rescue is unavailable. This effectively distinguishes it from other GPS rescue parameter setters.

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 implies usage is for allowing arming without a GPS fix, but does not provide explicit guidance on when to use this vs. alternatives (e.g., leaving it OFF for safety). No when-not or alternative tools are mentioned, placing it at a mid-level.

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