Molarity

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

The annotations already declare this is a read-only, idempotent, non-destructive computation, so the safety profile needs no elaboration. The description adds a directionality constraint (input molarity vs. input mass) but says nothing about precision, rounding, or error conditions when inputs are inconsistent.

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: the relationship and formula lead, the two usage directions follow, and the scope caveat closes. Every sentence earns its place with no redundancy.

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 7 fully described parameters, no output schema, and annotations covering the safety profile, the description supplies enough for correct invocation. It could mention return units or precision, but nothing critical to calling the tool 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 every parameter including units and the 'give this or that, not both' exclusivity for mass/molarity. The description reinforces the exclusivity but adds no syntax or format detail beyond structured fields.

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 exact quantity relationship and even supplies the formula (mass g = M x L x g/mol), so the agent knows precisely which computation this performs. It is clearly distinct from siblings like dilution_c1v1, serial_dilution, or convert_units, which handle different kinds of solution math.

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?

It explicitly states both invocation modes: supply molarity to obtain mass, or supply mass to obtain molarity. It also scopes usage to laboratory calculations. It stops short of naming sibling alternatives or saying when another tool is preferable, so it falls just short of a 5.

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