calculate_pipe_flow_rate

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

No annotations are provided, so the description must disclose behavior. It mentions the Hazen-Williams formula but inaccurately states 'Returns: {C_coefficient}' as if it were an output, while the coefficient is actually derived from the 'material' parameter. No details about error handling, rate limits, or side effects are given.

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 short with two sentences. The first sentence effectively states the purpose, and the second is a cross-reference. It is front-loaded but the cross-reference could be omitted to improve conciseness.

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 tool has an output schema (per context signals), but the description only mentions 'C_coefficient' which is not a direct output field. Without seeing the actual output schema, the description should still clarify what the function returns; it fails to do so comprehensively and introduces confusion.

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?

All four parameters have descriptions in the input schema (100% coverage), so the description adds no additional meaning beyond the schema. The mention of 'C_coefficient' in the description is about output, not parameters, and provides no new parameter insight.

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 'Calculate water flow rate through a pipe using the Hazen-Williams formula,' which identifies the specific action, resource, and method. However, it does not differentiate from the many other 'calculate_' tools on the server, so it lacks sibling distinction.

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 only usage guidance is 'See list_bundles for related 'plomberie' calculators,' which vaguely hints at a category but does not specify when to use this tool versus alternatives or provide any exclusion criteria.

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