set_rpm_limit_value

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

With no annotations, the description carries the burden. It discloses the data type (UINT16), default value (18000), and prerequisite. However, it does not specify whether the value persists across reboots, what happens if the required feature is disabled, or any validation beyond the schema's min/max. Adequate 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 a single sentence with a parenthetical for requirements and defaults. It is front-loaded with the main purpose, and every phrase adds value—no fluff. Exceptionally concise.

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 single-parameter setter, the description covers the purpose, parameter semantics, default, and prerequisite. It could briefly mention the relationship with set_rpm_limit (the feature toggle) for full context, but the provided information is sufficient for correct usage.

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?

The schema covers the parameter with a description and type, but the description adds the default value of 18000 and the unit context (RPM), which are not in the schema. This additional information helps the agent understand the expected value beyond the schema's generic description.

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 tool's purpose: setting the maximum motor RPM when `rpm_limit` is ON. It includes the specific resource (rpm_limit_value) and verb (Set), distinguishing it from siblings like set_rpm_limit (which likely enables/disables the feature) and other set_* tools.

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 clear context: it notes that this setting applies 'when rpm_limit is ON' and explicitly lists the prerequisite `Requires: USE_RPM_LIMIT`. While it doesn't explicitly say when not to use it or name alternatives, the condition is sufficient for an agent to decide.

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