get_gps_rescue_alt_mode

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

No annotations provided, so the description must carry behavioral info. It discloses the possible return values and default, which is helpful. It does not explicitly state it is read-only, but 'get' implies that. No side effects are mentioned, which is acceptable for a read operation.

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 a single sentence that efficiently explains the purpose, possible values, and default. No unnecessary words; every part adds value. Well-structured and easy to parse.

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 simplicity of the tool (no parameters, no output schema), the description fully covers what the agent needs: what the tool retrieves, what the possible values mean, and the default. No 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?

The tool has zero parameters, so schema coverage is 100%. The description goes beyond by explaining the meaning and default of each return value, which adds significant value since there is no output 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 the tool retrieves the gps_rescue_alt_mode and explains each possible value (MAX_ALT, FIXED_ALT, CURRENT_ALT) with brief definitions. The verb 'get' and resource 'gps_rescue_alt_mode' are explicit, and it distinguishes from related settings like set_gps_rescue_alt_mode.

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?

Usage is straightforward: call to read the current altitude mode. No explicit when-not or alternatives are needed, as the tool has no parameters and is a simple getter. The sibling setter provides clear complement. However, no explicit guidance on when to use vs. other getters, but it's implied.

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