set_tpa_curve_stall_throttle

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 adds the default value (30) and data type (UINT8), and notes the compile-time requirement. However, it does not disclose side effects, persistence, range bounds, or whether the change takes effect immediately.

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, well-structured sentence that conveys all essential information without extraneous words. It is front-loaded and efficient.

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 single-parameter mutation tool with no annotations or output schema, the description covers the purpose and parameter semantics but omits details like effective range (0-100 implied), behavior on invalid input, and clear differentiation from many sibling tools.

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?

The input schema only describes the parameter as 'Value for tpa_curve_stall_throttle (UINT8)', but the description adds meaningful context: it is a throttle percentage for stall detection. This significantly improves understanding beyond the schema.

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 the throttle percentage below which the craft is considered stalled, specifically for wing/fixed-wing TPA. It distinguishes this from other TPA-related tools by specifying the stall threshold purpose.

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 it is for wing/fixed-wing TPA and requires the USE_ADVANCED_TPA compile option, giving some context. However, it does not explicitly state when to use this tool versus alternative TPA curve tools or 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.