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

Annotations already declare this is read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by naming the returned fields (amount, readable amount, common packages, factor used, safety line) and clarifying that it is a calculation helper rather than a shock or LSI tool.

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 front-loaded with the use case and is generally dense with relevant information. The chemical list is long but largely earns its place because it maps products to treatment goals; slightly tighter structure could improve readability.

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 rich annotations, 100% schema coverage, and presence of an output schema, the description is complete enough for correct selection and invocation. It covers purpose, supported scenarios, exclusions, units, and return content without requiring the agent to infer missing behavior.

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 is already 3. The description still adds semantic mapping beyond the enum names, explaining which chemicals correspond to free chlorine, salt chlorination, alkalinity, stabilizer, calcium hardness, and pH changes, and clarifying units as ppm or pH.

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 states a specific action and resource: calculating how much pool chemical to add to move from a current to a target level. It enumerates the supported chemical/use cases and explicitly excludes shock targets and water-balance (LSI) questions, making its scope clear.

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?

It opens with a clear use condition ('Use this when someone asks how much...') and lists the supported chemical scenarios. It also gives explicit exclusions ('Not for shock targets or water-balance (LSI) questions'), so the agent knows when not to invoke it.

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