set_gyro_calib_duration

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

No annotations are present, so the description must disclose behavioral traits. It only says 'Set' without explaining whether this triggers recalibration, requires reboot, or is persistent. Minimal information beyond the set 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 brief and front-loaded, with essential details in one sentence plus a bracketed summary. It is efficient but could benefit from better structure (e.g., separate sentences for steps, range, and default).

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, the description covers the core aspects: purpose, units, range, and effect of value. However, it lacks details on persistence, immediate action, or interaction with other settings, which might be needed for full 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 covers the value's type and range, but the description adds crucial context: unit (0.1s steps), mapping example, effect on accuracy, and default (125). This significantly enhances understanding beyond 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?

The description clearly states 'Set gyro_calib_duration', specifying the verb and resource. It explains units (0.1s steps) and gives an example (125 = 12.5s), making it unambiguous. It distinguishes from siblings by naming the specific 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?

It mentions 'Longer = more accurate offset measurement', hinting at when to use larger values, but does not explicitly state when to use shorter durations or alternatives like set_gyro_calib_noise_limit. No trade-offs or exclusions are provided.

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