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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds only that it returns a converted flow rate, which is close to restating the title; no note on precision, rounding, or invalid-unit handling.

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?

Four short sentences, front-loaded with the conversion scope before domain context and I/O. 'Returns converted flow rate' is mildly redundant given the output schema, but nothing else is wasted.

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?

With a full output schema and 100% parameter coverage, the description only needs to establish scope and it does. The one gap is the 'L/s' unit claimed in the description that the from_unit/to_unit enums do not offer, which could mislead an agent.

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 100% with enums on both unit parameters, so the schema already carries parameter meaning. The description merely names the three inputs and adds no format, range, or unit-token guidance beyond the schema.

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?

States a specific verb (convert) and resource (flow rate) and enumerates the exact unit set, which cleanly separates it from neighbors like calculate_pipe_flow_rate, calculate_pressure_convert, or convert_volume. An agent can identify this tool without opening the schema, despite the listed 'L/s' not appearing in the enum.

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?

Offers domain context ('plumbing, HVAC, or industrial design') and a pointer to list_bundles, but never says when to prefer this over sibling converters or when it is inapplicable. Usage is implied by domain rather than stated as a condition.

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