pipe_pressure_drop

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals the underlying equations (Colebrook-White for turbulent, 64/Re for laminar) and that defaults are for water. However, it does not disclose the output format, whether both friction factor and pressure drop are returned, or any limits or side effects, which are gaps for a computational tool.

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 concise—two sentences—with the core computation front-loaded in the first sentence. It avoids fluff and imparts essential context (equations, defaults) efficiently, though it could be more structured with explicit output details.

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?

For a tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks information about return values, units for all inputs, and any preprocessing or error conditions. The agent would need to infer expected behavior, making this insufficiently complete for confident 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?

Schema description coverage is 0%, so the description must compensate. It explicitly mentions the roughness parameter (in meters) and indicates density and kinematic viscosity default to water values, which adds meaning beyond the schema. However, it doesn't explain velocity, diameter, or length, or the optional parameters in any depth, leaving the agent partially uninformed.

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 Darcy friction factor and Darcy-Weisbach pressure drop/head loss for pipe flow, which specifies a precise verb and resource. It distinguishes itself from siblings like heat_transfer_pipe by explicitly naming the equations, but it doesn't explicitly contrast with other tools, so it's not a full 5.

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 gives a passing hint about setting roughness for rough pipes and defaults for water, but provides no explicit guidance on when to use this tool versus alternatives (e.g., flow_regime, heat_transfer_pipe). No exclusions or conditions are stated, leaving the agent to infer usage.

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