set_gyro_calib_noise_limit

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

With no annotations provided, the description must fully convey behavioral traits. It states that calibration restarts if movement exceeds the threshold, which is key. However, it fails to mention whether the setting is persistent, if a save is required, or if it takes effect immediately. More context would improve transparency.

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 plus a parenthetical with range and default. Every word adds value. The purpose is front-loaded, making it easy for the agent to quickly understand the tool's function.

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 and no output schema, the description is reasonably complete. It explains the parameter, its effect, and usage advice. However, it lacks mention of related tools (e.g., get_gyro_calib_noise_limit) or any confirmation step, which would be helpful for full autonomy.

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% (the single 'value' parameter is described). The description adds practical guidance on when to increase the value, going beyond the schema's type and range. This helps the agent determine the correct parameter value in context.

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 the tool's purpose: setting the gyro calibration noise threshold, which affects calibration behavior. It explains that if movement exceeds this threshold, calibration restarts, and provides guidance for noisy environments. This distinguishes it from many sibling set_* tools by specifying the exact resource (gyro_calib_noise_limit) and its effect.

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 includes a practical usage guideline: 'Increase if it won't calibrate in a noisy environment.' This tells the agent when to adjust the parameter. However, it does not explicitly state when not to use the tool or mention alternatives (e.g., using the getter first). Nevertheless, for a simple setter, this is adequate.

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