set_gps_rescue_descend_rate

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

No annotations provided. The description gives the parameter range and default but fails to mention side effects like persistence, reboot requirements, or whether the change takes effect immediately.

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 short and includes the essential information in one sentence plus a bracket. The redundant repetition of the tool name is minor waste, but overall it is concise.

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 setter, the description covers the value range and context. However, it lacks information about how the setting is applied (e.g., immediate effect, requires save) which would be useful for completeness.

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% with a proper description. The tool description adds context ('Descent rate when approaching home') that goes beyond the schema's technical specification.

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 it sets the descendent rate during GPS rescue approach, but it starts with the tool name repeated, which is slightly redundant. It provides the type, range, and default, making the purpose clear.

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 vs siblings. It implicitly suggests use during GPS rescue configuration, but does not mention alternatives like ascend rate or descent distance.

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