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

No annotations are provided, so the description carries the full burden. It does disclose the identifier vocabulary and the conditional mw requirement, but says nothing about invalid/unknown conversion names, case sensitivity, precision or rounding of results, or how failures are reported. Useful behavioral context, but material gaps remain for a 30+-mode dispatch tool.

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 tight sentences: purpose, concrete examples, then the conditional parameter rule. Zero filler and the most important information is front-loaded.

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?

An output schema exists so return values need not be explained. For a tool whose main parameter accepts an unenumerated set of 30+ conversion strings, though, a partial example list leaves the agent unable to know whether its chosen string is valid; error and casing behavior are also absent.

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 0%, so the description must compensate. It explains mw (for mass-mole conversions) and gives six example values for the free-form 'conversion' string, which is the highest-risk parameter since it has no enum. It does not document api_key or the value parameter's units, and 6 of 30+ accepted conversion strings left the agent guessing.

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?

States a specific verb and resource ('Unit conversion for chemistry') and enumerates representative conversion identifiers, so an agent knows exactly what class of operation this is. It is clear without opening the schema, though it never explicitly distinguishes itself from the sibling covabasic_convert_format, whose name invites confusion.

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 sentence 'Pass mw for mass-mole conversions' is a genuine conditional instruction, telling the agent when one argument becomes necessary. However, there is no when-to-use-vs-alternatives guidance and no mention of the sibling convert_format, so usage is only partially implied.

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