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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds useful context with the calculation formulas and a one-credit cost, but it does not clarify that effectively one of growth_rate or doubling_time must be supplied or how conflicting inputs are handled.

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?

A single front-loaded sentence states the purpose and formulas without filler. The credit cost is compactly appended and does not distract from the core definition.

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?

For a four-parameter calculation tool with no output schema, the description is nearly complete: it names the formulas and inputs. It could more explicitly state that one of growth_rate or doubling_time is required in practice, but the formulas make the intended usage clear.

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 schema already documents each parameter. The description adds meaning by showing how time, growth_rate, doubling_time, and initial_population fit into the exponential growth formulas, clarifying the relationship between the two optional rate parameters.

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: calculates bacterial population after elapsed time. The inclusion of both exponential formulas distinguishes it from generic calculators and siblings like project_population or calculate_cell_density, though it does not name an alternative explicitly.

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?

Usage is implied by the tool name and formula, but there is no explicit when-to-use guidance, no mention of when to choose doubling_time versus growth_rate, and no named alternatives among the many calculate_* siblings.

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