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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine scope information the annotations cannot convey — that availability, rates and booking data are NOT returned — which prevents the agent from overselling what this tool provides. It stops short of describing volume/size of the response, so not a 5.

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?

Three short blocks, each front-loaded with its key point: what is returned, what is required, what is excluded. Zero filler, and the exclusion note is placed last where it is easy 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?

Annotations cover safety, an output schema documents the return shape, and 100% schema coverage handles parameters. The description's remaining job — scope, prerequisite, and explicit exclusions — is fully discharged, leaving no ambiguity for an agent invoking this tool.

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 100%: hotel_id carries a format example (PAR-87155) and language enumerates values plus the French fallback. The description reinforces the hotel_id origin ('as returned by search_hotels') but adds no new syntactic or semantic detail beyond the schema, so the baseline 3 applies.

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 ('Return the complete details of one hotel') and enumerates the payload fields, which distinguishes it from siblings get_hotel_photos and get_amenities that cover subsets. An agent can tell immediately this is the full-record retrieval tool.

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?

Gives an explicit precondition ('Requires a valid hotel_id') plus the alternative to run when the ID is unknown ('call search_hotels first'). It also states a clear when-not: no availability, rates or booking, and redirects the agent to page_url/contact details instead.

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