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

With no annotations, the description carries full burden. It only states 'Returns chlorine grams' but does not disclose any behavioral traits like read-only nature, precision, or edge cases (e.g., negative values). For a calculation tool, minimal disclosure.

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?

Two sentences: purpose and inputs. No fluff. Could be improved by aligning units and adding brief output description.

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?

Tool is simple with 3 params and output schema exists. Description covers inputs but unit inconsistency and lack of behavior details make it only adequate. References sibling list_bundles for related tools, which adds context.

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 has 100% coverage. Description lists inputs but says 'pool volume m³' while schema uses volume_liters (liters), causing unit inconsistency. Otherwise adds value by naming parameters but the mismatch reduces clarity.

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?

Clearly states the tool computes chlorine dosage for pool maintenance, with specific verb 'compute' and resource 'pool chlorine'. It distinguishes from siblings like calculate_pool_volume by its specific focus.

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?

Merely says 'Use for pool care' which is vague. No guidance on when to use this versus other related calculators (e.g., calculate_pool_volume) or when not to use it.

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