Cerca Dati

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does convey the input constraint (1-3 parole chiave), the output structure (titolo, ente, fonte e URL), and the real-data nature. However, it does not mention potential network dependencies, timeouts, or how results are ranked or limited — typical for a search tool but absent here.

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 compact and front-loaded: the core function appears in the first clause, followed by input limits, output content, and use cases. Every sentence adds value with no redundancy.

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?

For a single-parameter search tool, the description covers function, data sources, input requirements, output fields, and target use cases. An agent has enough to decide when to invoke it and what to pass. The presence of an output schema further reduces the need to explain return formats.

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?

With 0% schema description coverage, the description fully defines the only parameter 'parole_chiave' by giving format guidance (1-3 keywords) and concrete examples ('ponte stretto', 'qualità aria', 'bilancio comune'). This adds meaning far beyond the bare string type in the schema.

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 uses a specific verb ('Cerca') and a clear resource ('dataset di dati pubblici REALI sui portali open-data italiano ed europeo'), making its function unambiguous. It also names the specific portals (dati.gov.it, data.europa.eu), which distinguishes it from sibling tools that search legislation, statistics, or parliamentary records.

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 explicitly states when to use it ('Usa per opere pubbliche, costi, bilanci, appalti, ambiente, statistiche o numeri/fatti verificabili'), providing clear context without excluding any specific alternatives. It stops short of naming when NOT to use it or pointing to sibling tools, but the use cases are sufficiently specific.

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