Tripadvisor Reviews

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It only says 'Fetch Tripadvisor reviews', with no details on rate limits, pagination, authentication, or async behavior. The mention of a 'documented endpoint' is vague and does not reveal outcomes of using the tool.

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 a single sentence, so it is concise, but it is under-specified and does not fully earn its place. It conveys the basic action but omits crucial context that would help the agent, making it minimal rather than effectively streamlined.

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?

Despite having 8 parameters and an output schema, the description does not provide sufficient context. It fails to mention that multiple URLs can be processed, the async/execution_mode mechanics, or any differentiation from sibling review tools. The description is too thin for a tool this complex.

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 explains parameters like query, cutoff, reviews_limit, and execution_mode. The description adds no extra semantic value beyond what the schema provides, so the baseline of 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 'Fetch Tripadvisor reviews', which clearly identifies the action and resource. It also references the specific endpoint '/tripadvisor-reviews'. However, it does not distinguish from sibling tools like tp_reviews or booking_reviews beyond the name itself, so it lacks explicit differentiation.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that Tripadvisor URLs are required, nor does it explain when to prefer it over other review-fetching tools. No exclusions or scenarios are provided.

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