set_rpm_limit

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

No annotations provided. Description mentions value type (INT8) and default (OFF) but does not disclose persistence, immediate vs. reboot effect, or side effects. Basic transparency but incomplete.

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?

Single sentence with parenthetical requirement, efficiently front-loads action and constraints. No wasted words.

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 without output schema or annotations, description covers purpose, requirement, value type, default. Lacks details on immediate vs. reboot effect 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 describes value parameter as string (100% coverage). Description adds meaning by specifying expected INT8 type and default value, enhancing clarity beyond schema alone.

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 it enables per-motor RPM limit, with verb 'Set' and specific resource 'rpm_limit'. It distinguishes from sibling tools like get_rpm_limit (get) and set_rpm_limit_* (tuning parameters).

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 prerequisite (USE_RPM_LIMIT required), but lacks explicit comparison with alternatives or when-not-to-use. However, the tool's simple nature makes usage fairly clear.

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