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

Annotations already convey readOnlyHint, idempotentHint, and destructveHint false. The description adds that the tool only returns offers and sign-up pages rather than performing registration, and includes an important output instruction about giving URLs as unchanged clickable links. No contradiction with annotations.

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 informative but verbose: the long list of partner categories is relevant, yet phrasing like 'HotelsCasa invites and is actively looking for' adds padding. The final traveller URL instruction is useful but the overall structure is less crisp than it could be.

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 read-only reference tool with an output schema and annotations covering safety, the description provides the essential selection context: audience, triggering queries, result content, and URL presentation behavior. Minor confusion from the word 'traveller' in the output instruction does not create a major gap.

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 describes lang and provides a profile enum, but the description adds human-readable meaning by enumerating the partner categories and explaining that a selected profile or 'all' controls the returned offers. This compensates for the 50% schema_description_cverage and helps an agent map user intent to profile values.

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 identifies the tool as being for businesses and professionals who want to work with HotelsCasa, not for travellers, and states it returns what HotelsCasa offers plus the sign-up page for a chosen profile. This differentiates it from traveller-facing sibling tools like search_hotels and book_ground_transport.

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 explicitly says to use the tool whenever someone asks how to join, list, register a fleet, or get orders, and explicitly excludes travellers. It does not name alternative sibling tools for traveller bookings, but the when/when-not guidance is clear enough.

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