tripadvisor_reviews

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

Description states it returns normalized public reviews without credentials, indicating read-only operation. However, no details on rate limits, pagination behavior, or response format. With no annotations provided, the description carries the burden but misses some behavioral context.

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?

Two concise sentences effectively convey purpose and key input requirement. No redundant information; every word earns its place.

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?

With 10 parameters and no output schema, the description is insufficient. It does not explain pagination, sorting, filtering, or return format, which are critical for correct usage. The tool is more complex than the description suggests.

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 has 100% description coverage, so baseline is 3. Description adds value by noting 'Pass either id or url', but does not elaborate on other parameters. Minimal extra meaning beyond schema.

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?

Description clearly states 'Get TripAdvisor reviews' with specific verb and resource. It distinguishes from sibling tools (e.g., tripadvisor_place, tripadvisor_hotels) by focusing on reviews. The mention of 'normalized' and 'credential-free GraphQL' adds specificity.

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?

No guidance on when to use this tool vs alternatives like tripadvisor_place or tripadvisor_hotels. The description only says 'Pass either id or url' but does not explain when to choose which, nor when not to use the tool.

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