calculate_motor_params

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

No annotations exist, so description carries full burden. Only states calculation purpose; does not disclose any behavioral traits (e.g., side effects, permission needs, accuracy limits). Minimal transparency beyond function.

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?

Two sentences, front-loaded with purpose, followed by output context. No extraneous words; efficient and structured.

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?

Adequately describes inputs and outputs for a calculation tool. Could mention that poles must be even or that rotor speed should be below synchronous speed, but not essential given output schema presence.

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 covers parameters with descriptions (100% coverage). The description does not add meaning beyond the schema; baseline 3 is appropriate.

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 it calculates motor operating parameters from nameplate and measured data, listing specific outputs (synchronous speed, slip, rotor frequency, slip frequency). Distinguishes from sibling tools like compute_bearing_frequencies by noting outputs are prerequisites for fault frequency calculations.

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?

Implicitly conveys usage: when motor parameters are needed for fault frequency calculations. Does not explicitly state when not to use or provide alternatives, but the context with sibling tools clarifies its role.

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