venue_search

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

No annotations are present, so the description carries the full burden. It only states the basic action (search) and does not disclose behavioral traits such as rate limits, authentication requirements, result ordering, pagination, or error handling. The description is too minimal for a tool with no annotation backing.

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 a single sentence of 14 words, highly concise and front-loaded. It communicates the core purpose and key feature (location awareness) without any extraneous information. Every word earns its place.

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 simple search tool with 3 parameters and no output schema, the description covers the essential purpose. However, it omits details such as result format, pagination, or behavior when no results are found. Given the tool's low complexity, it is nearly complete but could be slightly more informative.

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?

The input schema covers 100% of parameters with clear descriptions. The description adds 'by name' and 'optional location awareness', but these only reinforce what the schema already provides. No additional syntax, validation rules, or examples are given, so the description adds only marginal 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 'Search for venues (breweries, bars, restaurants) by name, with optional location awareness'. It provides a specific verb ('search') and resource ('venues'), enumerates types, and distinguishes from sibling tools like search_brewery and search_beer. The mention of location awareness adds differentiation.

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 searching venues by name with optional location, but it does not explicitly state when to use this tool over alternatives like search_brewery or search_beer. No guidance on when not to use or prerequisites is provided, leaving the agent to infer from context.

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