set_crash_limit_yaw

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

No annotations provided, so description must convey behavioral traits. It states the parameter and range but does not disclose side effects, whether changes require reboot, or constraints like dependency on crash recovery being enabled. Minimal behavioral insight beyond the action.

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—one sentence with additional info in brackets. It front-loads the action and key attributes. There is no unnecessary text, and every piece of information earns its place.

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 single-parameter setter, the description covers the essential aspects: what it sets, units, range, and default. However, it lacks any broader context about crash recovery or when this parameter matters. Still adequate given the simplicity and presence of sibling tools for crash settings.

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 description adds value beyond the schema by specifying units (deg/s), range (0–1000), and default value (200 per profile). This extra context helps the agent understand the parameter semantics more fully.

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 explicitly states the action 'Set crash_limit_yaw' and explains its purpose: 'Yaw rate limit during crash recovery (deg/s).' It also includes units, range, and default value, making it clear what the tool does. Distinguishes from siblings by specifying the exact parameter.

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 on when to use this tool vs alternatives. Among many set_ tools, there is no mention of prerequisites, related settings, or whether to use the getter first. The description lacks context for optimal tool selection.

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