set_dyn_idle_min_rpm

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

With no annotations, the description adds context (enable by non-zero, target by prop size) but lacks details on persistence, side effects, or state requirements. Adequate but not thorough.

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, front-loaded with the parameter name, and every sentence adds value 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 setter with one parameter, the description explains the parameter, enable condition, and selection method. It could explicitly state that zero disables, but it's 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 coverage is 100%, but the description adds the default value and targeting guidance beyond the schema's basic type and range.

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 action 'Set dyn_idle_min_rpm' and explains its function as 'Minimum motor RPM maintained by dynamic idle'. 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?

Provides guidance on when to enable ('Set non-zero to enable') and how to target the value ('Target by prop size'), but does not explicitly exclude other tools or compare to alternatives.

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