calculate_solution_dilution

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

No annotations exist, so the description carries full burden. It explains that the tool computes and returns stock volume and diluent volume, which is adequate for a simple calculation tool. However, it does not disclose any edge cases, restrictions, or behavior for 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?

The description is brief (two sentences) and front-loaded with the formula and use case. It efficiently conveys key information with no verbose repetition.

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?

Given the lack of annotations and the presence of an output schema (not described in depth), the description is insufficiently complete. The input mismatch undermines trust. It fails to explain the return structure beyond mentioning two volumes, and does not cover how the tool handles incomplete or borderline inputs.

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?

The description claims 'Inputs: stock concentration, target concentration, target volume.' However, the input schema has c1, v1_ml (initial volume), and c2 (target concentration). There is no 'target volume' parameter; the description contradicts the schema and misleads about what input is required. Schema coverage is 100%, but the description adds incorrect information.

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 lab solution dilution using C1·V1=C2·V2 for stock-to-working solution prep. It lists inputs and outputs, making the purpose unambiguous. However, it does not differentiate from the sibling tool 'calculate_dilution', which may have similar functionality, so a perfect 5 is not warranted.

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 explicitly says 'Use for stock-to-working solution prep,' providing a clear usage context. It references 'list_bundles' for related calculators, indicating related tools, but does not specify when not to use this tool or name direct alternatives.

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