verify_lithium_origin

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

With no annotations, the description carries the full disclosure burden. It does add real value by revealing the evaluation logic and thresholds (SC6.0 to LiOH <= 2.5% loss, FEOC cap < 25% clean origin), but it says nothing about read-vs-write behavior, what a failure result looks like, or whether a verification is recorded or stateful. Some behavioral substance, significant gaps remain.

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?

A single dense sentence that front-loads the verification target before the evaluation criteria. No filler, though the stacked acronyms (SC6.0, IRA 30D, FEOC) compress a lot into one line.

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?

For a 12-parameter, 6-required tool with no annotations and no output schema, the description covers the domain well but omits what the verification returns, how pass/fail is signaled, and when the optional MINEDEX ID is needed. An agent would still need to probe the response shape.

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 83%, so the schema already documents nearly all parameters with examples and defaults. The description adds no parameter-level syntax or format detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 a specific verb (verifies) and a tightly scoped resource (Australian hard-rock spodumene to lithium hydroxide provenance), then enumerates the three concrete checks it runs (MINEDEX geofencing, stoichiometric mass balance, IRA 30D FEOC origin). This scope clearly separates it from siblings like verify_nickel_origin, verify_cobalt_origin, and verify_mineral_lot_compliance.

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 explains what is evaluated but never states when to reach for this tool versus the sibling verification tools, nor any prerequisites (e.g., that MINEDEX tenement ID is optional, or that AU-origin lots are required). Usage must be inferred entirely from the domain naming.

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