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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the description carries less burden. It adds context about ordering by quality and including booking links, which is useful but not extensive. There is 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 concise with no wasted words. It begins with a clear statement of purpose, followed by usage guidance, then a parameter list. The structure is logical and front-loaded.

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?

Given the simple parameter set (2 parameters, 1 required), 0% schema coverage, and presence of output schema, the description covers input explanations and output content (ordered experiences with booking links). It is complete for the tool's purpose.

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 0%, so the description must compensate fully. It does so by explaining 'place' as a city or country with examples, and 'limit' as number of results with a maximum of 30. This adds complete meaning beyond the schema's type and default.

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 that the tool retrieves the best experiences and things to do in a destination, ordered by quality, with booking links. It distinguishes itself from sibling tools by focusing on a guided list of top activities, which is explicitly compared to 'compare_experience' and 'search_experiences'.

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 the tool: when the user is planning a trip or asking for top activities/experiences. It does not explicitly say when not to use it, but the sibling tools imply alternatives, and the guidance provided is clear and contextual.

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