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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond those: 1–2 year data lag, annual updates, SDMX 2.1 format, CC BY 4.0 license, and no auth required. Nothing contradicts the annotations.

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 dense but well-organized: action and dataset first, then units, pollutants, parameters, temporal coverage, and source/license. Every sentence contributes operational knowledge and there is no filler or repetition of the schema.

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?

Given the full input schema, rich annotations, and presence of an output schema, the description is highly complete. It covers source, geographic scope, pollutants, units, time coverage, update frequency, licensing, and authentication requirements.

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 coverage is 100%, so the schema already documents all three parameters. The description still adds useful semantics: GHG means all greenhouse gases combined in CO2-equivalent, values are in million tonnes, country codes follow ISO 3166-1 alpha-2, and data availability from 1985–present informs the since_year parameter.

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 opens with a specific verb and resource: "Retrieve annual greenhouse gas emission inventories for EU/EEA countries from Eurostat (dataset: env_air_gge)". It also specifies the exact pollutant types, units, and geographic scope, making the tool's purpose unmistakable and distinct from Eurostat2 siblings covering different topics.

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 gives clear operational context: annual national emissions, ISO country codes, EU27_2020 aggregate, time coverage with lag, update cadence, and no-auth access. It does not explicitly name alternatives or when-not-to-use, but the topic and data details make selection versus other statistical tools straightforward.

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