eudr_generate_dds

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the output is an XML package and mentions EUDR-compliance, and 'generates' implies a creation operation. However, it does not disclose side effects (e.g., whether it stores the document, submits it to TRACES-NT, or merely composes the file), rate limits, or what the package contains besides a reference ID. Acceptable but gappy.

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?

The description is one clean sentence with no filler, front-loading the artifact name and compliance target. It earns its place, though it could benefit from a second sentence on behavior or use context.

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 generation tool with 5 required params and no output schema or annotations, the description is thin. It tells the agent the artifact and compliance framework, but not what the XML package is used for, how it relates to the sibling export tool, or what the agent can expect in return. The required params are all self-describing, so this is a minimum-viable definition rather than a complete one.

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% and each parameter has a clear description, so the schema already carries the param meaning. The tool description adds 'EU TRACES-NT compliant' and 'official EUDR reference ID' context, which hints at why the parameters matter, but it does not add per-parameter semantic meaning. 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?

The description uses a specific verb ('Generates'), identifies the specific artifact ('EU TRACES-NT compliant Due Diligence Statement (DDS) XML package'), and provides a distinguishing detail ('official EUDR reference ID'). It is clear about the resource being produced. However, it doesn't explicitly differentiate from the sibling tool eudr_export_traces_xml, which sounds similar in function, so it is not a 5.

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 implies the tool is used when an operator needs a TRACES-NT compliant DDS document with an EUDR reference ID. This gives a clear context but does not state when to prefer this over eudr_export_traces_xml or any other sibling, nor does it list exclusion conditions or prerequisites.

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