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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing that prices are indicative and must be confirmed with the owner, that there is no booking commission, and that each result carries an id and a site link. These are real behavioral facts beyond the annotation layer, though return format and pagination behavior remain implicit.

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?

Front-loads the purpose, then adds price semantics, then the result contract in three dense but non-redundant sentences. No filler, though the text is tightly packed and slightly hard to scan.

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 13-parameter read-only tool with no output schema, the description supplies the key business rules and even describes the return payload (id + site link). Combined with a 100%-covered schema, an agent has what it needs; only ordering relative to siblings and pagination are left implicit.

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 coverage is 100%, so the baseline is 3, but the description adds genuine semantics: budget_max is per week vs per stay depending on whether dates are supplied, dates make prices exact and enable availability checks, and destination ambiguity triggers server-side choices. This materially supplements 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?

States a specific verb and resource with scope (recherche de locations de vacances à la montagne en France) and even names the inventory (chalets, appartements, studios, direct-from-owner). It implicitly separates itself from siblings by explaining that results feed get_rental_details and check_availability_and_price, so an agent can tell it apart without opening schemas.

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?

Explains the conditional semantics of use: without dates prices are weekly, with dates the price is the stay total, and omitting destination searches all areas. It routes onward to two named siblings via the returned id. It stops short of an explicit when-not/ordering statement (e.g. run this before the detail tools).

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