ta_get_location_reviews

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

Description adds useful behavioral context beyond annotations: explicit limit of 5 reviews per call and pagination via offset. Annotations already indicate readOnly and openWorld hints; description complements with practical constraints. No contradictions.

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?

Single sentence, no wasted words. Front-loaded with purpose and key constraint. Ideal conciseness for a simple tool.

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?

For a read-only list tool with no output schema, the description adequately covers limit and pagination. Could mention sorting (most recent) but implied. Missing details like review rating range are not critical.

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 covers all 4 parameters with descriptions. Description adds minimal extra: 'up to 5 per call' reiterates the limit parameter, and 'page with offset' matches offset description. No significant enrichment 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 the tool retrieves 'most recent reviews' for a TripAdvisor location, using specific verb and resource. It includes scope (up to 5 per call, pagination via offset). However, it does not explicitly differentiate from sibling tools like ta_get_location_details or ta_get_location_photos, though the reviews focus is implied.

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 (e.g., search tools for finding locations). No when-not-to-use or prerequisites mentioned. The description only states what it does, not the context for choosing it.

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