eudr_issue_statutory_exemption

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

With no annotations, the description carries the full burden. It usefully discloses the governing regulation and effective date and states that an official certificate is produced, but says nothing about permission requirements, whether the exemption evaluation can fail/deny, or side effects of issuing a certificate.

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 core action and regulation; every clause is informative. Slightly overloaded by combining evaluation and certificate generation into one unbroken sentence.

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 five-parameter, no-annotation, no-output-schema tool that issues an official certificate, the description omits what the returned certificate contains, whether evaluation precedes issuance, and failure conditions. The regulatory framing helps but does not fully close the gap.

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 five parameters are already documented, including HS code examples that mirror the description text. The description adds no syntax, format, or default behavior beyond what the schema provides, so baseline 3 applies.

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 gives a specific verb pair (evaluates exemption, generates certificate) and a concrete resource (EUDR Delegated Act statutory exemption for excluded commodities, with HS examples). It is clearly distinct from generic siblings like eudr_generate_customs_certificate, though it never names an alternative to disambiguate.

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?

Usage is implied by the scope ('excluded commodities such as bovine leather'), but there is no explicit statement of when to call this versus eudr_generate_customs_certificate or eudr_simulate_swe_c_customs_clearance, and no prerequisites or when-not-to-use guidance.

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