set_gps_rescue_descent_dist

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

No annotations are provided, so the description must disclose behavioral traits. It only states the parameter meaning and range but does not mention effects on flight behavior, required features (e.g., GPS rescue enabled), or mutability characteristics. The description is minimal and lacks depth.

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 front-loads the purpose, then provides type, range, and default. Every word adds value, and there is no redundancy or verbosity.

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 covers the core purpose and valid values. However, it could mention the broader GPS rescue context (e.g., that this parameter only affects behavior when GPS rescue is active). It is mostly complete but lacks a hint about the feature dependency.

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 input schema: it explains that the parameter controls the distance from home at which descent begins, while the schema only says 'Value for gps_rescue_descent_dist'. The range and default are also included, providing complete semantic understanding.

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 action ('Set'), the resource ('gps_rescue_descent_dist'), and defines the parameter as 'Distance from home at which descent begins'. This precisely differentiates it from sibling set_* tools that target different 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?

No explicit guidance on when to use this tool versus alternatives (e.g., other GPS rescue parameter setters). The description provides no context about prerequisites, order of operations, or scenarios where this parameter should be adjusted.

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