autopilot_set_heading

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

No annotations provided, so the description bears full responsibility. It discloses the heading range and indicates a write operation, but lacks details on side effects (e.g., whether autopilot must be engaged) or response behavior. Minimal but acceptable given simplicity.

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, no wasted words, front-loaded with action and resource. Slightly under-specified but efficient for a simple command.

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's simplicity and presence of an output schema (though not shown), the description covers basic purpose and input range. However, it omits context like prerequisites (e.g., autopilot master on) or effect on aircraft heading, which would help in simulation contexts.

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 must compensate. It mentions the parameter's range (0-359 degrees) but does not explicitly name 'heading_deg' or explain its units beyond degrees. Adequate, but could clarify that input is an integer.

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 heading bug') and the resource, with a specific range (0-359 degrees). It distinguishes from siblings that set altitude, vertical speed, or toggle master.

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 alternatives like autopilot_set_altitude or autopilot_toggle_master. Usage is implied, but no when-not or prerequisite conditions are mentioned.

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