EU Taxonomy sectors and objectives

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds a great deal beyond them: snapshot provenance with no network access, a returned snapshot_date, attribution line, a legal caveat about binding status, and an explicit injection-defense convention wrapping quoted remote text as data. That is exactly the kind of behavioral context an agent cannot get from structured fields.

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?

Content is front-loaded (what is returned comes first), but the two sentences are extremely long and run-on, packing return fields, provenance, legal notes, and injection handling into dense clauses. Every element earns its place individually, but the packaging is hard to scan.

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 no output schema, the description carries the burden of describing returns, and it does so well: activity counts, objective abbreviations, criteria counts, delegated act/annex, snapshot_date, attribution and legal note. What is missing is any sense of output ordering or shape (e.g. list vs nested structure), which would help an agent plan consumption.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing to disambiguate and the description correctly does not invent parameter guidance.

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 concrete resource (sectors with activity counts) plus a second resource (the six environmental objectives with abbreviated codes and criteria counts). The verb is implicit in the tool name but the content is specific enough that an agent knows what it returns. It does not explicitly distinguish itself from siblings like `sources` or `criteria`, but the described payload is distinct.

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: this is the taxonomy overview/reference listing, useful before drilling into `get_activity` or `criteria`. However, there is no explicit when-to-use statement, no when-not-to-use, and no named alternative for the same need. The agent must infer the routing from sibling names alone.

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