calculate_flow_rate_convert

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that the tool returns a converted flow rate, without detailing validation, error handling, or any side effects. This is insufficient for a tool with no annotations.

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 composed of three concise, front-loaded sentences that cover purpose, usage context, and inputs/outputs. No extraneous information is present.

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?

Given the simplicity of the conversion tool and the presence of an output schema, the description covers the essential aspects: what it converts, when to use it, and its parameters. It also mentions a related tool. Minor gaps exist in behavioral details, but overall it is adequate.

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 100% and each parameter is already described in the schema with enums. The description merely restates 'value, from-unit, to-unit' without adding new semantic meaning. Per guidelines, baseline 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 explicitly states the conversion between specific units (L/s, L/min, L/h, m³/h, gpm, cfm) and identifies use cases like plumbing, HVAC, and industrial design. It clearly distinguishes from sibling tools by referencing list_bundles for related calculators.

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 provides context by suggesting usage for plumbing, HVAC, or industrial design, and directs users to list_bundles for related conversion calculators. However, it does not explicitly state when not to use this tool or compare it directly to other conversion tools like convert_volume.

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