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

With no annotations, the description carries the full burden of disclosure. It mentions the catalog contains duration and indicative price, but does not disclose behavior such as whether all excursions are returned when no filters are applied, pagination, or read-only status. The description is honest but not deeply transparent.

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, concise sentence that front-loads the tool's purpose ('Catalogo escursioni') and includes all essential details without waste. Every phrase 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?

Given the simple 2-parameter schema and no output schema, the description adequately covers the output fields (duration, price) and filter dimensions. It omits optional parameter behavior and return structure, but for a list tool the description is reasonably complete.

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 schema has 0% description coverage, but the description explicitly names both parameters ('isola' and 'categoria') and lists the valid category values. This compensates well for the lack of schema-level descriptions, though the island values are only available in the enum.

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 the tool provides a catalog of excursions filtered by island and category, with duration and indicative price per person. It distinguishes itself from sibling tools like dettagli_escursione (details) and riepilogo_catalogo (summary) by focusing on the list itself.

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 implies usage for browsing excursions by island or category, but it does not explicitly state when to choose this tool over alternatives like dettagli_escursione. No exclusionary guidance is provided, so the usage context is only implicit.

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