tripadvisor_search

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

No annotations provided, so description bears full burden. It mentions 'returns normalized TripAdvisor place listings' but does not disclose safety (e.g., read-only nature), rate limits, authentication requirements, or pagination behavior. The term 'normalized' is undefined, leaving behavioral uncertainty.

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: first states the action and resource, second details the output. No redundant language. Information is front-loaded and efficient.

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 tool has 20 parameters, no output schema, and complex filters, the description is insufficient. It does not explain how to use filters, interpret results, or handle large result sets. The absence of output schema makes the return format unclear.

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 coverage is 100%, so all parameters have descriptions. The description does not add additional meaning or examples beyond what the schema already provides. Baseline score 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?

Description clearly states 'Search TripAdvisor places' and enumerates return types: hotels, restaurants, attractions, and supported attractions. Differentiates from siblings like tripadvisor_hotels, tripadvisor_place, and tripadvisor_autocomplete by specifying it returns 'normalized place listings' across multiple categories.

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?

Description implies use when searching for TripAdvisor places but does not explicitly state when to use this tool versus specific tools like tripadvisor_hotels or tripadvisor_place. No exclusion criteria or alternative recommendations are provided.

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