tripadvisor_place

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

No annotations provided, so description carries full burden. Discloses browser fallback behavior but omits other traits like data richness, rate limits, or required permissions. Partially adequate but incomplete.

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?

Succinct two-sentence description. Front-loaded with purpose. No wasted words, but lacks structured breakdown.

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?

No output schema and no annotations. Description should explain more about the profile content, error behavior, or prerequisites. Incomplete for a retrieval tool.

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% with both parameters documented. However, description adds no additional meaning beyond 'url' and 'id' labels. Fails to clarify when to use each or their relationship.

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?

Clearly states 'Get TripAdvisor place' with a specific and distinct verb-resource combination. Differentiates from siblings like tripadvisor_search and tripadvisor_hotels. Mentions 'rich normalized profile' adding 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 explicit guidance on when to use this tool versus alternatives like tripadvisor_search or tripadvisor_hotels. The mention of browser fallbacks is behavioral, not usage context. Lacks exclusion or condition hints.

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