set_thrust_linear

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

No annotations are provided, so the description carries the burden. It explains the effect (linearises thrust curve, improves low-throttle authority) and notes 'no effect above mid-throttle'. However, it does not disclose whether the change is persistent across reboots or takes effect immediately, which are relevant behavioral traits for a set tool.

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?

Two sentences plus a parenthetical constraint. The description is front-loaded with the action and resource. Every word provides value without redundancy. No unnecessary details.

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?

The tool has a single parameter and no output schema. The description explains the parameter's purpose, typical usage, and range. It is sufficient for an agent to use the tool correctly, though a note on persistence or side effects would improve 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%, but the description adds meaning beyond the schema: it explains that the parameter linearises the thrust curve and suggests typical values (20–40%). This additional context helps the agent understand the parameter's role and appropriate range.

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 starts with 'Set thrust_linear', clearly indicating the verb and resource. It explains the purpose: 'Linearises the thrust curve at low throttle' and states benefits. Among many set_* siblings, this one is distinguished by its unique parameter and effect description.

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 provides context on when to use: 'especially for whoops and 48kHz ESCs', and typical range '20–40% is typically enough'. It does not explicitly state when not to use or mention alternatives, but the guidance is clear and helpful.

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