set_gps_rescue_ground_speed

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

No annotations are provided, so the description carries full burden. It indicates a write operation ('Set') but does not disclose side effects, persistence, or validation details beyond the schema's min/max. The behavior is adequate for a simple parameter setter, but lacks added behavioral context.

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 (one sentence plus a parenthetical), front-loads the purpose, and contains no fluff. Every part earns its place.

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 single-parameter tool with no output schema, the description covers the purpose, parameter meaning, range, default, and a usage tip. It could mention that this is for the GPS rescue feature, but that is implied by the name. Overall, it is fairly complete.

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%, so baseline is 3. The description adds value by providing a real-world conversion (750 ≈ 27 km/h) and a usage tip (reduce for wind). This goes beyond the schema's description of 'Value for gps_rescue_ground_speed (UINT16, 0–3000)'.

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_ground_speed parameter and defines it as 'Forward speed during return (cm/s)'. It provides a conversion example (750 ≈ 27 km/h) and a usage hint. The naming and context distinguish it from sibling tools like set_gps_rescue_ascend_rate.

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 gives explicit guidance: 'Reduce for reliability in windy conditions.' It implies when to use (when adjusting GPS rescue speed) but does not explicitly state when not to use or compare to alternatives. However, the tool name and sibling context make its purpose clear.

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