set_imu_process_denom

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

No annotations are provided, so description carries the full burden. It discloses that higher values reduce CPU load and degrade accuracy, and provides valid range (1-4) and default (2). It does not mention side effects like instant-apply or need for reboot, but for a simple parameter setter this is adequate.

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?

Description is extremely concise: two sentences and a format hint. It conveys purpose, behavioral effect, range, and default without any filler. Front-loads the parameter name and its role.

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 parameter setter with one parameter, the description provides all essential information: what it does, valid range, default, and trade-off. There is no output schema, but that is expected for a setter. Missing details like persistence or reboot requirement are minor for this domain.

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 has 100% description coverage for the only parameter ('value'). The description adds meaning beyond the schema by explaining the parameter's function as a rate divisor and its performance trade-off, which the schema's description ('Value for imu_process_denom') does not provide.

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?

Description clearly states tool sets the IMU attitude update rate divisor. It explains the parameter's role relative to gyro task rate, distinguishing it from the many other set_* tools in the sibling list. The verb 'Set' and specific resource 'imu_process_denom' provide unambiguous purpose.

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?

Description explains effect of higher values (reduce CPU load at cost of attitude accuracy), giving implicit guidance on when to use (need performance vs accuracy trade-off). It does not explicitly state when not to use or mention alternative parameters, but the trade-off context is sufficient for this simple setter.

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