get_rpm_limit

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

No annotations are provided, so the description carries full burden. It describes the setting's type (INT8) and default (OFF), adding context beyond the empty schema. However, it does not explicitly state that the tool is read-only or disclose any side effects or behavioral traits.

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 additional details in parentheses, no wasted words. It is front-loaded with the tool name and purpose.

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?

The description lacks information about what the tool returns. As a getter with no output schema, it should explain the return value (e.g., current value of rpm_limit). It only describes the parameter itself, not the tool's output.

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?

With zero parameters, baseline score is 4. The description does not need to add parameter semantics, and it appropriately mentions the type and default for the setting itself.

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 retrieves the rpm_limit setting that enables per-motor RPM limit. It is specific about what the tool does, though it could be more explicit that it reads the current value. Among many sibling get_ tools, it is distinguishable by its focus on rpm_limit.

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 mentions a prerequisite (USE_RPM_LIMIT) but provides no guidance on when to use this tool vs alternatives like set_rpm_limit or get_rpm_limit_value. No when-to-use or when-not-to-use information is given.

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