Dilution C1V1 = C2V2

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is largely covered. The description adds value beyond that: it discloses the returned diluent volume and the consistent-units requirement, and scopes it to laboratory use. Return-format detail is limited but annotations carry most of the profile.

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?

Three short sentences, front-loaded with the core operation, then the input rule, then the side output and scope note. No filler, every sentence earns its place.

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 partly compensates by noting the diluent-volume return, and it explains the input rule and units. It could say more about what the primary solved value looks like, but for a simple four-number utility it is essentially complete.

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 baseline is 3, but the description adds a constraint the schema does not express: required is 0 and all four params are optional in the schema, yet the description mandates exactly three be supplied. It also imposes a units-consistency rule, which is meaningful semantics beyond the field docs.

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 states a specific operation (solve C1 x V1 = C2 x V2 for the single missing value) and adds a secondary output (diluent volume). It clearly distinguishes itself from a multi-step tool like serial_dilution in spirit, but never names a sibling to route the agent 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?

The rule 'give exactly three of c1, v1, c2, v2 in consistent units' is a real invocation constraint, so usage is more than implied. However, it gives no when-to-use vs alternatives — nothing tells the agent why to pick this over serial_dilution or reconstitution_concentration.

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