pump_power

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

No annotations are provided, so the description carries the burden. It discloses that shaft power is only computed when an efficiency is supplied, which is useful behavioral context. However, it omits details such as output format, units, or error behavior.

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?

A single, front-loaded sentence with no redundant words or fluff. It is appropriately concise for the amount of information conveyed.

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?

An output schema exists, so return values need not be described. However, the tool has no annotations and minimal description, leaving out usage guidance, unit conventions, or broader context that would help an agent select it confidently.

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 0%, so the description must compensate. It clarifies that pump_efficiency is optional and alters the output to include shaft power, but it does not explain the meaning or units of the three required parameters beyond their self-descriptive names.

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 identifies the tool as computing hydraulic power and optionally shaft power when efficiency is provided. It distinguishes itself from siblings like pump_tdh and pump_npsha, which focus on head and NPSH rather than power, though it lacks an explicit verb.

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 implies usage by naming the calculation, but it does not explicitly say when to use this tool versus alternatives. The conditional phrase 'when an efficiency is supplied' hints at a mode switch, but there are no direct usage scenarios or exclusions.

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