set_tpa_speed_pitch_offset

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

No annotations are provided, so the description bears full responsibility. It indicates the tool sets a configuration parameter and notes the required feature, but does not disclose whether changes are persistent, require a reboot or rearm, or take effect immediately. The behavioral impact is unclear.

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 concise with two sentences. The first sentence states the purpose, and the second adds the requirement and type/default info. It is front-loaded and contains no redundant information.

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 it is a simple setter with one parameter and no output schema, the description could provide more context such as units, typical values, or persistence behavior. It mentions 'pitch offset correction' but does not explain the effect of different values, limiting completeness.

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%. The description adds context that the value is a 'pitch offset correction' and states the default is 0, which is beyond the schema's minimal description. However, it does not specify units, allowed range (beyond being an INT16), or how the value relates to other parameters.

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 it sets the tpa_speed_pitch_offset parameter, a pitch offset correction for speed TPA on wing/fixed-wing trim. It is specific enough to distinguish from other set_* tools, though it does not explicitly differentiate from sibling tools.

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 mentions the prerequisite 'Requires: USE_WING', which gives a condition for use. However, it provides no guidance on when to use this tool compared to alternatives like set_tpa_breakpoint or other speed TPA settings, nor does it explain when not to use it.

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