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

With no annotations, the description carries the full burden and does well: it declares determinism, offline public-domain sourcing, source-returning behavior, and the 'found=false (never a guess) when unknown' contract, plus the kind-listing fallback. It omits auth/permission requirements and any rate/limit context, which keeps it from a 5.

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?

Front-loads the core purpose and packs the kind enumeration efficiently. Some phrasing is redundant ('consolidated like verify into one tool', 'The agent twin of GET /lookup') and could be trimmed, but the description is not bloated.

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?

No output schema and no annotations, yet the description covers return semantics ('Returns the value + its source') and the unknown-result case, so an agent has what it needs to call correctly. Minor gaps around auth and per-kind edge behavior keep it just under 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 0%, so the description must compensate, and it does by enumerating the kind values and their expected params (molar_mass {formula}, element {symbol|name|atomic_number}, convert {value, from, to}). The generic params object structure is only implied rather than described, so it falls short of full documentation.

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 ('Look up a VALUE deterministically from the engine's offline, public-domain data') and explicitly positions it against the sibling verify ('the found-value twin of verify'). An agent can distinguish it from verify and the other lookup-like siblings (define, resolve, find_verifier) without opening a schema.

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?

Gives a clear use pattern ('look it up, then verify it') and a fallback ('Call with an unknown kind to list the current kinds'). It names verify as the counterpart but does not fully spell out when to prefer lookup over the many other lookup-ish siblings, so it stops short of explicit when-not/alternatives.

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