calculate_pool_chlorine

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

With no annotations, the description carries the burden of behavioral disclosure. It implies a pure calculation with no side effects, but does not explicitly state safety, idempotency, or permissions. The simple nature of a calculator tool makes this minimally adequate.

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 succinct with three sentences, clearly front-loaded with the core purpose. No unnecessary words, and the reference to list_bundles is brief.

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?

Despite good schema and output schema, the description has a unit inconsistency (m³ vs liters) and omits default values for parameters. A more complete description would clarify units and mention defaults.

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% with clear parameter descriptions. The description merely restates the inputs without adding new information like valid ranges, units (note inconsistency: description says m³ but schema uses liters), or parameter relationships.

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 tool computes chlorine dosage for pool maintenance, specifying inputs and output. However, it does not explicitly distinguish from sibling tools like calculate_pool_volume, though the name is specific.

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 minimal guidance, only stating 'Use for pool care' and a vague reference to list_bundles for related calculators. No explicit when-to-use or when-not-to-use is given.

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