search_attractions

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

With no annotations, the description bears full burden. It explains parameters and defaults but doesn't disclose error handling, result limits, or pagination behavior beyond the 'page' parameter. The behavior is simple and expected for a search 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 concise with a clear header and bulleted Args list. No wasted words; each sentence adds value. The purpose is front-loaded.

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's simplicity and presence of an output schema, the description is fairly complete. It covers purpose, parameter semantics, and prerequisite. It could add sortBy options or error examples, but is sufficient for correct use.

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 0%, so description compensates well. It explains 'id' as base64 encoded from another tool, 'sortBy' default trending, 'page' default 1. It lacks possible sortBy values but provides essential meaning beyond raw 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?

The description clearly states it searches for attractions/tours in a specific location, with verb 'Search' and resource 'attractions/tours'. It distinguishes from sibling tools like 'search_attraction_locations' (for getting IDs) and 'get_attraction_details' (for details).

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?

The description indicates the tool should be used after obtaining the 'id' from 'search_attraction_locations', providing a clear usage context. It does not explicitly state when not to use it, but the prerequisite is clear.

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