calculate_pipe_diameter

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

No annotations are present, so the description must carry the full burden. It only states the calculation purpose without disclosing behavioral traits such as assumptions (e.g., pipe material, formula) or side effects. The return format is not described, though output schema exists.

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 concise sentences: first states the core purpose, second provides a pointer to related tools. No extraneous information.

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 is simple with a full schema and output schema. The description covers the basic functionality but omits context like unit consistency or formula assumptions. Adequate but not thorough.

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 covers 100% of parameter descriptions (flow_rate_lpm and max_velocity_ms described clearly). The description adds no new semantic information beyond the schema; it only restates the overall purpose. Baseline of 3 is appropriate.

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 verb 'calculate' and the resource 'minimum pipe diameter' with inputs flow rate and max velocity. It references related calculators via list_bundles, suggesting differentiation from sibling tools like calculate_pipe_flow_rate, but does not explicitly distinguish itself.

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?

No direct guidance on when to use this tool versus alternatives. Only a vague reference to 'list_bundles' for related calculators, which does not explicitly state when NOT to use this tool or name specific alternatives.

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