set_tpa_speed_adv_prop_pitch

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

No annotations are provided, so the description must carry the full burden. It claims the value is UINT16, but the input schema allows integers from -9e15 to 9e15, contradicting the description. This is a serious inconsistency. Additionally, no side effects, validation behavior, or persistence details are disclosed. The contradiction lowers the score to 1.

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 a single sentence with a requirement note and type/default in brackets. It is front-loaded with the action and resource, and every element (name, unit, requirement, default) is essential. No wasted text.

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 single-parameter setter, the description provides the unit, default, and prerequisite. However, the annotation contradiction undermines completeness, and there is no explanation of typical values or the parameter's impact on flight behavior. Adequate but with clear gaps.

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% (one parameter). The description adds the unit (mm), default value (370), and data type hint (UINT16) beyond the schema's minimal description. This provides meaningful additional context, earning a score above the baseline 3.

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') and the resource ('tpa_speed_adv_prop_pitch: Propeller pitch (mm) for ADVANCED speed TPA physics model'). The unit (mm) and default (370) are provided. This distinguishes it from sibling tools like set_tpa_speed_adv_drag_k or set_tpa_speed_adv_mass which configure different parameters.

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 includes a prerequisite: 'Requires: USE_WING'. This tells the agent when the tool is applicable. However, it does not specify when not to use it or suggest alternatives among the many TPA-related siblings. The guidance is helpful but incomplete.

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