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

With no annotations, the description must convey the tool's behavior. It implies a read-only overview, but does not explicitly state that it makes no changes or returns only summary data. The lack of a side-effect statement keeps this at a 3.

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 a single sentence with a colon separating the main purpose from the specifics, followed by a short usage note. Every phrase adds value, and it is front-loaded.

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 tool with no parameters and no output schema, the description sufficiently explains what the tool returns (counts per island, min price, first departure) and when to use it. Nothing essential 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?

The tool has zero parameters and an empty schema. The description adds no parameter-related meaning because there are none. Per the rubric, 0 parameters gets a baseline of 4.

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 clearly states that the tool provides an overview of the active catalog, including number of offers per island, minimum price, and first available departure. This distinguishes it from sibling tools like cerca_offerte and dettaglio_offerta by focusing on aggregate summaries. However, it lacks an explicit verb like 'get' or 'list', so it falls short of a 5.

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 provides a clear use case: answering the question 'cosa avete?' (what do you have?). This gives context for when to invoke the tool, but it does not explicitly mention when not to use it or compare with alternatives, so a 4 is appropriate.

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