set_crash_gthreshold

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only repeats the parameter's range and default from the schema. Missing details on persistence, required reboot, or any interaction with other crash detection parameters.

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 single sentence that packs all essential information: purpose, parameter meaning, data type, range, and default. 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 setter with one parameter, the description covers the parameter meaning, range, and default adequately. However it could mention if changes take effect immediately or require a reboot to complete contextual 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 semantic value: it explains the parameter's role (gyro rate threshold for crash detection), provides the unit (deg/s), and states the default value (400 per profile), which are not in 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?

Clearly states the tool sets crash_gthreshold, the gyro rate threshold for crash detection. The description includes the unit (deg/s) and range, distinguishing it from numerous sibling set_ tools by specifying the exact parameter and its meaning.

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 versus alternatives like set_crash_dthreshold or set_crash_delay. No context on prerequisites, such as whether the craft must be disarmed, or when this setting should be adjusted.

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