autopilot_set_vertical_speed

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

The description only states the basic action without disclosing side effects. With no annotations provided, it fails to reveal important details such as whether setting vertical speed changes autopilot modes, requires autopilot engagement, or has any limits.

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?

A single sentence with no wasted words. It efficiently conveys the core purpose and key parameter semantics.

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?

While the tool has an output schema, the description does not reference return values or error states. It omits context like prerequisites (autopilot state) and mode interactions. For a simple one-parameter tool, the description is minimally adequate but incomplete.

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 0%, so the description bears full responsibility for clarifying the 'fpm' parameter. It explains its meaning (vertical speed in feet per minute) and sign convention (negative=descend), but lacks details like typical range or validation rules.

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 action ('Set the autopilot target vertical speed'), specifies units ('feet per minute'), and explains sign convention ('negative = descend'). It distinguishes from sibling tools like autopilot_set_altitude or autopilot_set_heading by focusing on vertical speed.

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 like autopilot_set_altitude. No mention of prerequisites (e.g., autopilot must be engaged) or conditions (e.g., vertical speed mode required).

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