set_tpa_speed_adv_drag_k

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

No annotations are provided, so the description carries full burden. It states the data type (UINT16) and default value, but fails to disclose whether the setting persists, requires a reboot, or has immediate effects on flight behavior. The parameter schema permits values far outside UINT16 range, which could mislead the agent.

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 one sentence plus parenthetical notes. It avoids redundancy but could be better structured with separate sections for purpose, prerequisite, and defaults.

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 setter with one parameter, the description covers the core purpose, prerequisite, type, and default. However, it lacks context on persistence, side effects, or how this parameter interacts with other TPA settings, which would be useful for a safe agent invocation.

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 description for the single parameter. The tool description adds the default value (1000) and clarifies the type and requirement, which is valuable beyond the schema. However, it does not specify the valid range or units for the coefficient.

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 aerodynamic drag coefficient for the advanced speed TPA physics model. It distinguishes this parameter from other TPA settings through the name and mentions the 'ADVANCED' model, but does not explicitly differentiate from sibling tools like set_tpa_speed_adv_mass.

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 notes the prerequisite USE_WING but provides no guidance on when to use this tool vs alternatives like other TPA parameters. There are no 'when not to use' statements or comparisons with other set_tpa_* tools.

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