calculate_electrical_power

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

No annotations exist, so the description carries the burden. It mentions return values (kW and kVA) but omits side effects, auth requirements, or error behavior. Since it's a stateless calculation, a 3 is adequate.

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 plus a referral to bundles. The first sentence front-loads the purpose. Efficient but includes generic 'Use for electrical engineering' that adds little value.

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 context includes an output schema (unseen) which helps. However, with many sibling calculators, the description lacks differentiation. The referral to list_bundles is minimal. Not fully complete for an agent to know when to prefer this tool.

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%, so the schema already documents parameters. The description lists inputs but adds no extra meaning beyond the schema fields (e.g., units or constraints not already in schema). Baseline 3 applies.

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 computes electrical power for single or three-phase circuits, with specific inputs and outputs. This verb+resource combination is precise and distinct from sibling 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?

Only says 'Use for electrical engineering', which is vague. No explicit when-to-use or when-not-to-use, and no direct comparison to alternatives. The hint to see list_bundles is indirect.

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