takeoff

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

The description discloses important behavioral traits such as altitude validation against a configured ceiling with a default value, and the asynchronous nature of the operation. Since no annotations are provided, the description carries the full burden, and it handles this well, though it could also mention safety implications or error conditions.

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 well-structured and concise, providing essential information in three focused paragraphs: purpose, usage constraints, and return value. Every sentence adds value without redundancy.

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?

Given the tool has an output schema, the description provides adequate context about the return value and asynchronous behavior. It covers prerequisites, restrictions, and cited alternatives, making it complete for a complex tool.

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?

The description adds meaning to the parameters, explaining that 'altitude_m' is meters above launch point and validated against a ceiling, and that 'confirm' requires human approval. With 0% schema description coverage, the description fully compensates, though it does not list the exact default values from 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 that the tool makes the vehicle 'take off vertically to `altitude_m` meters above the launch point', providing a specific verb and resource. It distinguishes itself from sibling tools like 'land' or 'arm' by describing a distinct flight action.

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 explicitly states when the tool is rejected ('Rejected in readonly mode'), requires specific user confirmation ('confirm=true after human operator approval'), and lists prerequisites ('The vehicle must be armed first (call arm)'). It provides clear usage guidance without ambiguity.

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