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

Annotations already declare this a read-only, idempotent, non-destructive computation, so the safety profile is covered. The description usefully adds the output unit ('Returns chlorine grams'), but states volume in m³ while the schema requires volume_liters, which is actively misleading about how to invoke it.

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?

Three short sentences, front-loaded with the purpose and output unit, which is good. The final sentence about 'list_bundles for related construction calculators' does not earn its place for a pool-dosage tool and only adds confusion.

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?

An output schema exists, so explaining return structure isn't required, and the description covers purpose, inputs and output unit. However, the volume unit conflict, the unmentioned defaults, and the absent formula basis (ppm delta × volume) leave real gaps for a numeric tool where wrong units silently corrupt the answer.

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%, so the baseline would be 3, but the description contradicts the schema by labelling the volume input as m³ whereas the parameter is volume_liters (a ~1000x dosage error if trusted). It also omits the meaningful defaults on target_ppm (1.5) and current_ppm (0), which change results when omitted.

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 and resource ('Compute chlorine dosage (g) for pool maintenance') with the driving inputs, which is enough to separate it from the many sibling calculators and from calculate_pool_volume. It misses a clean differentiator against calculate_pool_volume and the closing pointer to 'construction' bundles is noise.

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?

'Use for pool care' is the only usage statement and it is essentially a restatement of the tool name. There is no when-not guidance, no mention of when to prefer calculate_pool_volume, calculate_dilution or the pH tools, and the list_bundles reference is a cross-sell, not an alternative-selection rule.

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