set_gps_rescue_initial_climb

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

With no annotations, the description carries full burden. It discloses the parameter's purpose and constraints (range, default) but lacks details on side effects (e.g., persistence, whether changes take effect immediately or require a reboot). The description is adequate but not comprehensive for a mutation tool.

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?

Two concise sentences plus a range note. Every sentence adds value: purpose, usage guidance, and constraints. No redundant or extraneous information.

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 and no output schema, the description is largely complete. It covers what the parameter does, how to set it, and its limits. It lacks mention of related parameters or persistence behavior, but these are minor omissions for this tool's simplicity.

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 description coverage is 100% but merely repeats the type and range. The description adds meaning by explaining the role of the altitude ('climb from current position before heading home') and the advisory to clear obstacles, which enhances the agent's understanding beyond the schema.

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 initial climb altitude for GPS rescue, with a specific verb ('Set') and resource ('gps_rescue_initial_climb'). It explains the purpose: climbing from current position before heading home, and distinguishes itself from numerous sibling 'set_' tools through its specific naming and context.

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?

Provides practical guidance on choosing the value ('Set high enough to clear local obstacles'), which helps agents decide on an appropriate parameter. However, it does not explicitly contrast with related tools like set_gps_rescue_return_alt or set_gps_rescue_alt_mode, nor does it state when not to use this tool.

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