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

The description frames the tool as a read-only retrieval ('Get full details', 'Returns all safety/suitability attributes'), but the annotations declare readOnlyHint=false. That is a material contradiction about whether the tool is read-only, despite otherwise useful disclosure about pricing, live availability, and booking links.

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 four compact sentences and is front-loaded with the core purpose. Each sentence earns its place: sibling routing, return contents, pricing caveat, and presentation instruction.

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?

There is no output schema, but the description supplies the important return semantics an agent needs: safety/suitability attributes, THB pricing with price_note guidance for per-person vs per-booking, live availability, and book_now_url. That is sufficient to call and present results correctly.

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%, and the single parameter is documented with an example format (exp_170728P24). The description only adds 'by ID' and 'pass its experience_id', which is consistent but does not add meaning beyond the schema, so the baseline score of 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?

The description states a specific verb and resource: 'Get full details for a specific experience by ID.' It also explicitly distinguishes the tool from the sibling search tool by positioning it for follow-up questions using an experience_id returned by 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?

It names the alternative tool and the exact condition for using this one: follow-up questions about products returned by search_experiences, passing its experience_id. This gives an agent clear routing guidance rather than leaving usage implicit.

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