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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds the computed outputs (stock volume and diluent volume), but an output schema also exists, so it contributes only modest extra context beyond the structured fields.

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?

Four short sentences, front-loaded with the core formula, with no filler. The 'See list_bundles' pointer is a reasonable trailing sentence. Slightly more than strictly needed but well structured.

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 3 fully documented required params, an output schema, and rich annotations, the description's only obligation is to state purpose, use, and relationship to relatives. It covers purpose, use, outputs, and a related-tools pointer; the input labeling inconsistency is the only meaningful gap.

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 baseline is 3. The description's input list ('stock concentration, target concentration, target volume') is slightly loose — v1_ml is defined in the schema as *initial* volume, and no target-volume parameter exists — so it adds little meaning and arguably muddles the mapping.

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 gives a specific verb+resource (compute lab solution dilution) and even supplies the formula C1·V1=C2·V2, which is far more concrete than a tautology. However, it does not distinguish itself from the very similar sibling calculate_dilution, which an agent would have no way to choose between from this text.

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?

'Use for stock-to-working solution prep' gives a clear usage context, but there are no exclusions and no routing to the near-identical sibling calculate_dilution. For a tool in a family of hundreds of calculators with overlapping names, the missing differentiation leaves real ambiguity.

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