eudr_generate_export_bundle

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

With no annotations provided, the description carries the full behavioral burden. It hints at a 'non-repudiation HMAC evidence seal' but never states whether the operation persists data, whether it is read-only or mutating, what auth/permissions are needed, cost, latency, or whether the bundle is generated on demand. 'Lawyer-proof' is marketing, not behavioral disclosure.

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?

It is a single front-loaded sentence that leads with the verb and resource, so an agent can parse intent immediately. The terms 'lawyer-proof' and 'One-Click' are brand/marketing padding that add little precision, keeping it out of the top tier.

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?

This is a complex composite tool taking a nested EUDRSupplyChainPayload with no output schema and no annotations. The description never says what the bundle actually is (a file, a URL, a JSON document), nor how the components are returned or whether failures in one component abort the bundle. For a tool of this complexity, that leaves a significant 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 the schema already documents the payload, producer_registry_id, and producer_country_code. The description adds no additional parameter semantics (no format, constraints, or interaction notes), so the baseline 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?

States a specific verb (Generates) and resource (EUDR One-Click Export Bundle), and enumerates the four components it combines (HMAC evidence seal, KFS readiness score, producer registry verification, export dossier), which distinguishes it from single-purpose siblings like eudr_generate_dds or eudr_export_traces_xml. However, it never explicitly names those siblings or contrasts the bundle with them, so sibling differentiation is implied rather than stated.

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 when-to-use guidance, no prerequisites, and no mention of the alternatives. Given that siblings eudr_score_kfs_checklist and eudr_verify_producer_registry cover parts of what this tool bundles, the description should have said when to reach for the composite instead of the individual calls, but it says nothing.

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