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

No annotations are provided, so the description carries the transparency burden. It discloses that the calculation is 'solved iteratively against pipe Reynolds number' and notes support for gas expansibility and permanent pressure loss. It does not mention limitations or failure conditions, but the key behavior and scope are well conveyed.

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 three sentences, front-loaded with the core calculation, followed by supported options. It is efficient overall, though the final 'Powered by multicalci.com' sentence is non-functional noise for an AI agent and slightly reduces the score.

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?

This is a complex tool (10 parameters, iterative solver) with no output schema. The description covers the standard, equation, tap types, fluid states, and pressure loss, giving a solid operational picture. It does not explicitly state the return values (beyond 'mass flow') or constraints like beta ratio limits, but it is reasonably complete for selection and invocation.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds context about the iterative equation and the role of Reynolds number but does not explain parameter relationships or unit expectations beyond what the schema already provides.

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 a specific action: 'Calculate mass flow through an orifice plate per ISO 5167-2 using the Reader-Harris/Gallagher discharge coefficient equation'. It names the exact resource (orifice plate), standard, and method, and it is immediately distinguishable from sibling tools like control valve sizing or pipe pressure drop.

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 specifying the calculation context (ISO 5167-2 orifice flow) and supported configurations ('corner, flange and D&D/2 taps, gas expansibility and permanent pressure loss'). It does not explicitly state when-not-to-use or name alternatives, but the scope is clear enough given the distinctive purpose.

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