get_altitude_source

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

No annotations are provided, so the description carries full burden. It mentions the return type as INT8 with default 'DEFAULT' but does not explain possible values (e.g., enum options), what 'DEFAULT' means, or any side effects. The description is minimal and lacks detail on what the agent can expect.

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 very short (one sentence plus a type hint), with no wasted words. It is concise but could be slightly improved by clarifying the 'Override' phrasing. Still, it is efficiently structured.

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?

No output schema is provided, so the description should explain the return value. It only states '[INT8, default: DEFAULT]' without mapping integer values to meanings or describing how the source affects behavior. The description leaves the agent with incomplete understanding of the tool's output.

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?

There are no parameters, so the baseline is 4. The description does not need to add parameter information, and it correctly omits any.

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 'Get altitude_source' and explains its purpose for overriding altitude data source for autopilot and OSD display. It distinguishes from sibling tools like 'get_altitude' (actual altitude) and 'set_altitude_source' (setter). However, the phrase 'Override altitude data source' could be misinterpreted as setting, causing slight confusion.

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. It does not mention that 'set_altitude_source' is for changing the value, or that 'get_altitude' is for actual altitude. Among siblings, there is 'get_altitude_prefer_baro' which might be related, but no differentiation is provided.

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