verify_rare_earths_origin

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

No annotations are provided, so the description carries the full behavioral burden. It never states what the verification returns, whether it fails/throws on non-compliance, whether it is read-only, what happens when thresholds are breached, or any auth/rate-limit requirements.

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 verb and the main compliance domains. It is appropriately sized, though the regulatory jargon (MOFCOM Notice 61, 0.1% extraterritorial) could be opaque without explanation.

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 an 8-parameter, all-required verification tool with no annotations and no output schema, the description is too thin. It does not explain the verification outcome, error behavior, or how the four compliance regimes interact, leaving significant gaps.

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 all eight parameters are already documented in the schema, including thresholds like >= 99.50% and <= 500 ppm. The description adds no parameter-level meaning beyond the schema, so baseline 3 is correct.

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 verb (verifies) and resource (Rare Earth Elements provenance) and enumerates the compliance regimes checked. It is clearly distinct from siblings like verify_tungsten_origin or verify_niobium_scandium_origin, though it never names them 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?

There is no guidance on when an agent should call this tool versus the other verify_* siblings, and no mention of prerequisites, ordering, or when NOT to use it. The description is purely declarative about scope.

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