set_gps_rescue_alt_mode

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

The description explains what each mode does behaviorally and warns that CURRENT_ALT is not recommended. However, it does not disclose whether changes are persistent, require a reboot, or affect other settings. With no annotations, the description carries the full burden but only partially addresses behavioral transparency.

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 very concise, using a colon-and-list format to explain three modes in two sentences. Every word adds value, and the default value and type are mentioned efficiently. 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?

Given that the tool is a setter with one parameter and no output schema, the description adequately covers the behavior of each mode. It lacks information about persistence or side effects, but for a simple configuration tool, this is sufficient. The sibling tool list is large, but the description effectively distinguishes this tool's purpose.

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 description adds significant meaning beyond the schema, explaining each possible value's behavior. The schema only says 'Value for gps_rescue_alt_mode (UINT8)', which is minimal. The description clarifies the semantics of each option, though there is a type mismatch (schema says string, description says UINT8) which slightly reduces clarity.

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 starts with 'Set gps_rescue_alt_mode', clearly identifying the verb and resource. It explains three distinct modes (MAX_ALT, FIXED_ALT, CURRENT_ALT), which distinguishes it from sibling tools like set_gps_rescue_initial_climb or set_gps_rescue_return_alt.

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 provide guidance on when to use this tool versus alternatives. Although it lists the modes, it lacks context on choosing one over another in a workflow, and no exclusions or prerequisites are mentioned.

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