Serial dilution

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

Annotations establish that this is a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses what is computed (transfer and diluent volume per tube) and the unit convention for outputs. It stops short of stating anything about edge behavior (e.g. rounding, invalid inputs).

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, both front-loaded with the substantive output information first and the unit rule second. The trailing 'For laboratory calculations only' adds little but costs only a clause.

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?

With no output schema, the description correctly takes on the job of describing the return values (per-tube concentrations, transfer and diluent volumes). Combined with a fully covered parameter schema and read-only annotations, an agent has what it needs to call it correctly; only cross-tool routing guidance is missing.

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 description coverage is 100%, so the schema already documents all four parameters with their constraints (factor > 1, steps 1-20, positive start_conc and volume). The description only adds the unit-mapping rule for start_conc, which is a small increment. Baseline 3 is appropriate.

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 names the specific resource (a serial dilution) and its outputs — per-tube concentrations plus transfer and diluent volumes. It is clearly distinguishable from single-step siblings like dilution_c1v1, though it lacks an explicit verb and doesn't name that sibling.

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 only guidance is the scope note 'For laboratory calculations only', which is a disclaimer rather than usage direction. There is no statement of when to pick this over dilution_c1v1, reconstitution_concentration, or the other siblings, and no exclusions.

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