eudr_link_downstream_chain

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

With no annotations, the description carries the full disclosure burden. It adds some behavioral colour ('eliminates redundant assessment costs', 'monitors cascading revocation/taint'), but says nothing about required permissions, whether it is a persistent write, idempotency, what happens when the upstream reference is invalid, or the failure/revocation semantics it claims to monitor.

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?

Two tightly written sentences, front-loaded with the core purpose and followed by the value proposition. No filler or repetition, though the second sentence blends benefits with behavior in a way that slightly muddies structure.

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 seven-parameter, compliance-critical mutation tool with no annotations and no output schema, the description covers the concept but omits the resulting state (what DDS reference or chain record is produced), side effects, and error behavior. Adequate but with clear gaps an agent would want filled.

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 all seven parameters, including the upstream_dds_reference format example. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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+resource: 'Implements ... downstream Due Diligence Statement (DDS) reference chaining,' naming the regulatory basis (EUDR Article 4(8)) and the mechanism (inheriting the upstream DDS reference). It is clear what the tool does but does not distinguish itself from DDS-related siblings such as eudr_generate_dds or eudr_export_traces_xml.

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 explicit when-to-use guidance, no prerequisites, and no named alternatives among the many DDS/compliance siblings. An agent must infer from the phrase 'downstream' and 'inherits upstream supplier DDS reference' that this is for downstream operators chaining onto an existing upstream DDS, but that inference is left entirely to the reader.

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