verify_black_mass_origin

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

With no annotations, the description carries the full behavioral burden. It discloses the compliance regimes checked (BIS license validity, EU recycled-content thresholds), which is useful context, but says nothing about what the tool returns, whether it is a read-only check or a recorded submission, how failures or below-threshold inputs are handled, or any rate/permission constraints.

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?

One dense sentence with the subject and the three verification targets front-loaded; nothing is wasted. It is arguably over-packed, but every clause earns its place by naming a distinct compliance dimension.

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 11-parameter, all-required verification tool with no annotations and no output schema, the description is under-specified: it never explains the required geolocation, the material-content parameters, or what a verification verdict looks like. The regulatory framing is present but the operational contract is not.

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 only 45%, so the description must compensate. It does explain the regulatory meaning of bis_export_license_id and recycled_content_ratio indirectly, but batch_id, facility_id, latitude, longitude, and the nickel/cobalt/lithium percentages are left with no guidance, and the >= 0.85 / <= 500 ppm constraints percolate only from the schema.

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?

Specific verb (verifies) applied to a specific resource (recycled battery black mass provenance), plus two further named checks (BIS export license, EU 2023/1542 recycled content). An agent can tell this apart from the mineral-specific siblings like verify_cobalt_origin or verify_composite_battery_passport by the black-mass framing and the BATTERY-regulation scope.

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?

No statement of when to use this versus verify_lithium_origin, verify_cobalt_origin, verify_composite_battery_passport, or verify_customs_clearance. No prerequisites, no exclusions, no mention of what an agent must have on hand before calling. Usage is only inferable from the domain nouns.

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