set_altitude_prefer_baro

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

With no annotations, the description carries the full burden. It discloses the data type (INT8), valid range (0-100), and default value (100). It explains the behavior of extremes, which is sufficient for a simple setter. It does not cover persistence or side effects, but such detail is not critical here.

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?

Description is extremely concise with two sentences, front-loading the key information (name, purpose, range, default). Every word is useful with no fluff.

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?

For a simple parameter setter with one integer parameter and no output schema, the description is complete. It covers what the tool does, valid values, default, and meaning of extremes. All essential information is present.

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 coverage is 100% with a single 'value' parameter described. The description adds semantic value by explaining the meaning of the range endpoints and the default, which goes beyond the schema's basic type and range constraints.

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 tool sets a weight parameter between barometer and GPS altitude, with explicit range and default. It uses the verb 'Set' and specifies the resource 'altitude_prefer_baro', distinguishing it from the getter sibling tool.

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 implicitly guides usage by defining the range meaning (0=GPS only, 100=baro only) and default. While it doesn't explicitly say 'use this tool when...', the context is clear for a simple parameter setting, and no alternative setter tool exists for this parameter.

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