search_venues

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

No annotations are provided, so the description must carry the full burden. It discloses that data comes from Eventflare and returns real venue names, pricing, capacity, photos, and booking URLs. However, it does not mention whether the search is read-only, rate limits, or pagination behavior, leaving some uncertainty about side effects.

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 somewhat lengthy but well-structured: opens with core function, then lists search criteria, return value, and data source. Every sentence adds useful information, though some could be tightened. It is front-loaded with the main purpose.

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 absence of output schema and annotations, the description covers essential aspects: what the tool does, input parameters (extensive examples), and return data. It could mention pagination or ordering, but it adequately sets expectations for a search 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%, so parameters are already well-documented. The description enriches understanding by providing concrete examples (e.g., city 'london', 'dubai') and mapping categories to event types (e.g., 'conference-venues' for conferences), adding value beyond the 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 finds corporate event venues with specific criteria, including cities, capacity, category, and event type. It differentiates from sibling tools like get_venue_details (for specific venues) and list_cities (just city listings) by focusing on search functionality.

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 implies usage for venue search but does not explicitly state when to use this tool versus alternatives like get_venue_details or find_expert_advice. There is no 'when not to use' guidance, though the context is clear.

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