set_gps_rescue_min_start_dist

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

With no annotations provided, the description fully discloses the behavioral impact: setting a distance threshold that, if violated, causes disarm and drop. This crucial safety context is clearly communicated, along with the data type, range, and default value.

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 concise and well-structured. It starts with the tool's purpose, follows with a clear safety note, and ends with the data specification. Every sentence adds value with no redundancy.

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 parameter-setting tool with full schema coverage, the description is complete. It covers the parameter's effect, safe usage, and technical constraints. No output schema is needed.

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?

Schema coverage is 100%, but the description adds meaning beyond the schema by specifying the value as UINT16 with range 5–30 and a default of 15. This helps the agent understand the expected input format and typical value.

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 sets the 'gps_rescue_min_start_dist' parameter and explains its purpose: 'Minimum distance from home to activate rescue.' It also describes the consequence ('Closer than this → disarm and drop'). This effectively distinguishes it from sibling tools like get_gps_rescue_min_start_dist and other GPS rescue settings.

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 implicitly explains when to use this tool: to prevent accidental rescue activation near home. It also implies the risk of setting the value too low. However, it does not explicitly state when not to use it or compare with alternatives (e.g., other rescue distance settings).

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