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

Annotations already establish read-only/idempotent/non-destructive behavior; the description adds genuinely useful operational details beyond those: no auth required, the public SDMX source URL, the ~4900-item scope, and the 200-result cap. These are exactly the behavioral facts an agent needs to call and consume the tool correctly.

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 three sentences with no filler. It front-loads the core action, then covers scope, topics, modes, cap, downstream use, source, and auth in a compact and well-ordered way. Every sentence earns its place.

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 simple list/search tool with one optional parameter and an output schema, the description is complete: it covers what the tool returns conceptually, how to filter, the cap, the data source, auth requirements, and how to use the result with sibling tools. Nothing critical is missing.

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 description coverage is 100%, so the schema already documents the query parameter with substring, case-insensitive, and examples. The description reinforces that query filters by name/id and that omitting it lists all dataflows, but it adds little meaning 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 opens with a specific action and resource ('Search or list ISTAT... dataflows') and explicitly names the domain (ISTAT economic/social statistics) and scope (~4900 series). It also names sibling tools (istat.structure, istat.data) that consume the returned dataflow_id, making the tool's role clear.

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?

It clearly explains the two modes of use (with or without query) and states the result cap. It also provides a downstream workflow ('Use the returned dataflow_id with istat.structure and istat.data'), which tells the agent how to chain calls. It does not explicitly discuss alternatives like adbkidb.explore.dataflows, but the ISTAT-specific framing is sufficient disambiguation.

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