set_motor_idle

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

With no annotations provided, the description carries the full burden. It discloses the range and default value, but does not mention persistence across reboots, required configuration mode, or side effects on other settings. Basic behavioral context is present but lacks depth.

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 exceptionally concise, consisting of two clear sentences and a compact bracketed range/default specification. Every word contributes meaning without redundancy.

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 a single required integer parameter and no output schema, the description covers essential information: purpose, role, range, units note, and default. It could mention that this is a persistent configuration parameter but is largely complete.

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 description coverage is 100%, so baseline is 3. The description adds value by providing the default value (550) which is not in the schema, enhancing the agent's understanding of typical values.

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 verb ('Set') and the specific resource ('motor_idle'). It explains that it sets the idle throttle value sent to ESCs when armed and is used as the minimum non-zero motor command, effectively distinguishing it from sibling tools like get_motor_idle and motor_set.

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 provides context about when the value is used (when armed) and its purpose (minimum non-zero command), but does not explicitly explain when to use this tool versus alternatives like set_min_command or set_motor_pwm_rate. No exclusions or alternatives are mentioned, leaving usage decisions somewhat ambiguous.

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