get_gps_rescue_min_start_dist

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

No annotations are provided, so the description carries the full burden. It discloses the behavioral consequence of the parameter (disarm and drop if too close), which goes beyond a simple parameter description and adds valuable context for the agent.

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 bracket note. It front-loads the key information and contains no filler or redundant content.

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 no output schema, the description adequately explains the parameter and its effect. It implies the tool returns the current value. Could explicitly mention that it returns the current value, but the meaning is clear.

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 0 parameters, so schema coverage is 100% (trivially). The description adds type, range, and default value in brackets, which provides meaningful context beyond the empty schema. Baseline for 0 params is 4.

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 gets the gps_rescue_min_start_dist parameter and explains its purpose as the minimum distance from home to activate rescue. It distinguishes itself from other get_gps_rescue_* tools by specifying this particular parameter.

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 explains the behavior of the parameter (closer than this leads to disarm) but does not explicitly state when to use this tool versus alternatives like the set_gps_rescue_min_start_dist or other get_gps_rescue_* tools. Usage context is implied but not directly addressed.

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