List MeteoEurope1km grid archives

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds genuinely non-obvious context — the data is free, hosted on an external service (Zenodo), GeoTIFF/COG format, Equi7 Europe EPSG:27704, Int16 scaled in tenths, NoData -9999. It does not disclose anything about the listing behavior itself: number of files returned, whether URLs or sizes are included, or whether results vary by product/variable combination.

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 short sentences with no filler; the dataset identity and geospatial/radiometric conventions are front-loaded. It is fragmentary rather than wasteful, though the second sentence is purely about raster decoding and slightly off-target for a listing tool.

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 should say what the agent gets back from a 'list' call (file names, year coverage, URLs, sizes), and it does not. Four parameters with two enums and a required variable make the selection logic non-trivial, and the description leaves all of it to the schema.

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 all four parameters (including enum meanings for product and variable) are already documented in the schema. The description only adds the unit context for the raster values (°C, mm, hPa, in tenths), which helps interpret variables but adds no parameter-level semantics beyond the schema. 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 identifies the resource precisely (MeteoEurope1km archives on Zenodo, Europe/1 km/1961-2020/COG) but never states the action — it never says it lists available archive files or what a returned entry contains. The verb 'list' exists only in the title and tool name, so an agent must infer that this returns a file catalog rather than metadata or a download link.

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 guidance on when to call this versus siblings such as download_gridded_files or estimate_area_download, nor any statement of prerequisites (e.g. that you must list before downloading). The only usage constraints live in the schema's parameter descriptions (years required for day/mon, period for normals), not in the description.

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