calculate_motor_torque

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

Discloses formula, units (N·m, lb-ft), and purpose. No annotations were provided, so description handles transparency well, though edge cases like zero power are not mentioned.

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?

Very concise (2 sentences + formula), front-loaded with action and formula. However, the unit mismatch (kW vs W) detracts from clarity.

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?

Explains calculation, units, and use case. Given output schema exists, describing return values is less critical. But missing handling of zero power or negative values, and unit inconsistency reduces completeness.

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% with descriptions for both parameters. Description adds formula and unit context, but introduces a mismatch: parameter is in watts (power_w) while description states 'power kW', which may confuse users.

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?

Clearly states the tool computes motor torque from power and RPM, with the formula, specific resource (motor torque), and distinguishes it from many sibling calculators by its mechanical focus.

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 explicit use case ('mechanical sizing') and points to related calculators via list_bundles, but lacks direct when-not-to-use or alternative tool comparisons.

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