set_tpa_speed_adv_thrust

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as whether the change is immediate, persistent, requires reboot, or how invalid inputs are handled. For a mutation tool, this is insufficient.

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 extremely concise, using a single sentence plus metadata in parentheses. It front-loads the purpose and includes type, default, and requirement in a well-organized manner with no wasted words.

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 configuration parameter with one input and no output schema, the description covers purpose, requirement, type, default, and unit. However, it lacks behavioral details (e.g., side effects, validation) that would be helpful given the absence of annotations.

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 schema description is minimal ('Value for tpa_speed_adv_thrust (UINT16)'), but the tool description adds the unit (g), default value (2000), and context (advanced model). This significantly enhances parameter 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 verb 'Set' and the resource 'tpa_speed_adv_thrust', defining it as 'Maximum thrust (g) for ADVANCED speed TPA physics model.' It distinguishes from siblings by specifying 'ADVANCED' and the unit, though it lacks explicit differentiation from similar advanced parameters like tpa_speed_adv_drag_k.

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_) and specifies the data type and default, but does not provide when-not-to-use guidance or compare to alternative tools like basic TPA settings or other advanced parameters.

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