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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions output (stock volume and diluent volume) but fails to resolve a key ambiguity: the input schema includes v1_ml labeled as 'Initial volume mL', while the description treats it as 'target volume'. This inconsistency undermines transparency, and no details about auth, rate limits, or edge cases are given.

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 very concise: three sentences that front-load the key formula and purpose. No redundant or unnecessary words.

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?

The tool is simple (one formula), and the schema covers parameters. An output schema exists but is not provided here; the description outlines outputs. However, the ambiguity between input and output volume definitions weakens completeness for a new user. It is adequate but not fully 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?

The input schema has 100% description coverage, so the baseline is 3. The description adds semantic labels ('stock concentration', 'target concentration', 'target volume') but creates confusion by mismatching the schema's 'Initial volume' label. Overall, it provides minimal additional value beyond the schema and introduces potential misinterpretation.

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 the formula C1·V1=C2·V2, for stock-to-working solution preparation. It specifies inputs and outputs, and distinguishes itself from a large set of sibling tools by naming the specific formula and application.

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 provides a clear usage context ('Use for stock-to-working solution prep') and directs users to related 'science' calculators via list_bundles. However, it does not explicitly state when not to use this tool or provide exclusions.

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