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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely useful behavior beyond them: results are the LATEST value per series with period, unit, source and page, not full time series — a distinction that matters against the leggi_serie sibling. It does not mention ranking or empty-result 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?

Two sentences, front-loaded with the core action and searchable facets, followed by the return shape. The trailing English fragment 'Italian agricultural and water data' is low-value repetition but costs little.

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 correctly compensates by describing what each result contains (latest value, period, unit, source, page). Combined with annotations, an agent has enough to call it and interpret the response; only result ordering and no-match handling are unstated.

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 both parameters are already documented with examples. The description adds only a small amount of meaning by clarifying that 'soggetto' can be a country, region, lake or river, which helps shape the free-text query. 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?

States a specific verb (Cerca) and resource (serie storiche di Oltre il Solco), names the subject domain and the facets searchable (indicatore, soggetto: Paese, regione, lago, fiume). It is distinguishable from elenca_indicatori and leggi_serie by implication, but the siblings are never named or contrasted explicitly.

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 and no mention of alternatives, even though leggi_serie is the obvious next step once a series is found. The only usage signal is implicit: phrase a topic query and the tool searches by indicator and subject.

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