set_gps_rescue_ascend_rate

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

Provides data type, range, and default but omits behavioral details such as whether the setting persists across reboots or takes effect immediately. No annotations to cover this gap.

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?

Single sentence plus compact bracketed info. Extremely concise and front-loaded with key details.

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?

Adequate for a simple single-parameter setter. Lacks context about GPS rescue mode and typical values, but sufficient for basic parameter setting.

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 covers 100% of parameters with type, min, max, description. Description adds the default value (750) and reiterates range, adding slight value beyond 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?

Clearly states the action (Set), resource (gps_rescue_ascend_rate), and specific purpose (climb rate during initial climb phase). Distinct from siblings like set_gps_rescue_descend_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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, typical scenarios, or relationships with other parameters.

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