Annex IV Technical Documentation Checklist

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description adds real value beyond them: it discloses that sub_items are non-binding implementation prompts, are not verbatim Annex IV text, and create no additional legal requirements. That is exactly the kind of content caveat an agent needs to avoid overstating legal authority, though it says nothing about output size or formatting behavior.

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?

Three sentences, no fluff, but the structure is inverted for a tool definition: it opens with a caveat about output contents rather than stating what the tool does or returns. Every sentence earns its place on legal accuracy, yet the most important information for selection (the core action) is absent, so front-loading is poor.

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?

With an output schema present, return values need not be described, and both parameters are fully documented in the schema, so nothing an agent needs to invoke it is missing. However, the description never states the core action or when to prefer it over sibling tools, leaving the selection decision weaker than it should be for a nine-sibling tool family.

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 baseline is 3, but the description adds legal meaning to sme_simplified by grounding it in Article 11(1) second subparagraph and the requirement to use the Commission form — context the schema's one-line description does not carry. The 'json' vs 'checklist' format parameter gets no added commentary, keeping it just above baseline.

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 implies this returns the Annex IV checklist by referencing 'the nine titles and descriptions' and 'sub_items', but it never states a verb+resource action such as 'returns the Annex IV technical documentation checklist'. It also gives no differentiation from siblings like euaiact_get_article or euaiact_get_obligations, which an agent could plausibly confuse it with for the same legal content.

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: nothing says to call this when preparing technical documentation under Article 11 or when auditing Annex IV coverage. The Article 11(1) SME sentence is a legal caveat about the domain, not a usage condition selecting this tool over an alternative.

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