get_gps_rescue_allow_arming_without_fix

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

No annotations provided, so the description carries full burden. It discloses that enabling this allows arming without GPS fix but makes GPS rescue unavailable, and OSD shows 'RESCUE OFF'. It also notes type and default, providing good behavioral context beyond the name.

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 plus a type/default tag. Front-loaded with the name and core purpose. No redundant information.

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 getter with no parameters and no output schema, the description covers the key behavioral impact and data type. It could mention that it returns the current value, but that is implicit. Overall complete enough.

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?

No input parameters, so schema coverage is 100%. The description adds meaning by explaining what the value represents (arming without fix, rescue unavailable) and includes type and default info, which is helpful beyond the schema.

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 it gets the gps_rescue_allow_arming_without_fix setting and explains what it does: 'Allow arming without a GPS fix.' This is specific and distinguishes it from sibling getters for other parameters.

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 does not explicitly guide when to use this tool or when not to. It implies reading the parameter value, but does not mention alternatives (e.g., set counterpart). For a simple getter, this is adequate but lacks explicit guidance.

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