set_yaw_rate_limit

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool sets a rate limit but does not mention whether changes take effect immediately, require a reboot, are persistent, or affect other parameters. For a simple setter, this is minimal; missing important behavioral context like side effects or persistence.

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, consisting of two brief statements. It front-loads the purpose and includes essential details (type, default). While there is no fluff, it could be slightly more structured (e.g., separate lines for type and default), but overall it respects the 'every sentence earns its place' principle.

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?

Given the simplicity of the tool (single parameter, no output schema, no nested objects), the description is adequate for a setter but incomplete. It lacks usage context, behavioral details, and does not explain the parameter's unit or valid range beyond schema constraints. A more complete description would include the unit (degrees per second?) and effect on flight behavior.

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%, and the parameter description already specifies it is an integer for yaw_rate_limit. The description adds the default value (1998) and reiterates the type (UINT16), which provides marginal added value. Per guidelines, baseline is 3 when schema coverage is high, and no additional semantic richness beyond the schema is provided.

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 it sets a 'Hard cap on yaw rate' and specifies the data type (UINT16) and default value (1998). It distinguishes the tool from many other set_* siblings, though it does not explicitly differentiate from similar rate limit setters (e.g., set_roll_rate_limit), which would be helpful but the naming convention already implies the resource.

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 guidance is provided on when to use this tool versus alternatives. The description does not explain the effect of changing this value, prerequisites (e.g., connected flight controller), or contrast with other set_* tools like set_yaw_rate_limit or set_roll_rate_limit. The agent receives no context for appropriate usage.

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