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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: results are newest first, each result includes the saved date, and pagination is cursor-based. It doesn't mention rate limits or auth, but for a read-only favorites list, the disclosed behavior is sufficient.

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 compact and front-loaded: it states the core purpose in the first sentence, then usage context, then return fields, then follow-up actions, then pagination. Every sentence earns its place and there is no redundant filler.

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?

The tool has an output schema, so return values are already structured. The description covers the key contextual needs: when to use it, what fields are returned, how to chain to sibling tools, and how to paginate. For a read-only favorites list with only two optional parameters, nothing essential is missing.

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%, so the schema already documents both parameters (limit and cursor). The description adds the context that the cursor comes from a previous get_favorite_hotels result and is used to fetch the next page, which slightly reinforces the schema. However, it doesn't add meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 states a specific verb ('Get'), a specific resource ('hotels the user has saved as favorites in Gondola'), and a clear ordering ('newest first'). It also distinguishes itself from sibling tools like search_hotels and get_hotel_details by focusing on favorites, so an agent can select it without ambiguity.

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 explicitly says when to use it ('when the user asks about their favorite or saved hotels, or to ground recommendations in places they already like') and provides a follow-up action ('Pass the returned hotel_id to get_hotel_details or get_hotel_rates'). It also explains pagination behavior with the cursor, which is a clear usage guideline.

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