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

With no annotations, the description carries the burden of behavioral disclosure. It adds a critical non-obvious behavior: the tool does not expose prices, and hotels are only sold within packages. This goes beyond simply describing the search function and helps manage expectations.

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 highly concise, using two short sentences. The first sentence front-loads the core purpose, and the second provides a key limitation. Every word earns its place, with no redundant information.

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 search tool with 4 optional parameters and no output schema, the description provides sufficient context: the search scope and the important price limitation. It does not explicitly state return format, but that is reasonably inferred. Overall, it is complete for typical usage.

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 50%, with only 'nome' and 'zona' having partial-match descriptions. The description lists all four filter dimensions (isola, zona, stelle, nome) but adds no extra meaning beyond the parameter names. It does not explain the enum values or the semantics of stelle_min, leaving some gap.

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 searches catalog hotels by island, zone, stars, or name. This specific verb+resource combination distinguishes it from sibling tools like cerca_offerte and lista_escursioni, making its purpose unambiguous.

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 when to use the tool: when searching for hotels by the listed criteria. It also provides an exclusion by stating that prices are not exposed and hotels are only sold within packages, guiding the agent away from using this tool for pricing queries. However, it does not explicitly name alternative tools.

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