set_thr_expo

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

No annotations are provided, so the description carries the full burden. It only repeats schema information (type, range, default) without disclosing any behavioral traits such as whether the change is persistent, requires reboot, or affects other settings. The agent learns nothing beyond the schema.

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?

Extremely concise at two sentences, front-loading the purpose and parameter constraints. 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 parameter set tool with one parameter, the description is minimally sufficient. However, it does not explain what throttle expo does or its impact on flight behavior, leaving the agent to infer from context. Could be more complete.

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%, so baseline is 3. The description adds 'Throttle expo' which explains the meaning of the parameter, and includes the type, range, and default value, going beyond the schema's minimal description.

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 'Set thr_expo: Throttle expo.' It specifies the verb ('Set'), the resource ('thr_expo'), and provides the parameter type, range, and default value in brackets. This distinguishes it from siblings like set_thr_hover or set_thr_mid.

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?

No explicit guidance on when to use this tool versus alternatives. However, the description implies it is used to configure throttle expo, and given the naming convention among siblings, usage is implicitly clear. Lacks prerequisites or when-not-to-use context.

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