yelp_search_events

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

The description does not disclose any behavioral traits beyond the fact that it searches for events. Since no annotations exist, the description should provide details about read-only nature, authentication requirements (api_key), rate limits, or response structure, but none are mentioned.

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 short sentence, which is concise but insufficiently informative. It sacrifices necessary detail for brevity, resulting in under-specification that harms usability.

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 has no parameter descriptions, no output schema, and operates among many sibling tools, the description is far from complete. It fails to equip the agent with enough context to use the tool correctly, such as how to authenticate or interpret results.

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?

With 0% schema description coverage, the description adds no meaning to any of the four parameters (location, categories, start_date, api_key). It does not explain expected input formats, default behavior, or the purpose of each parameter, leaving the agent without critical usage information.

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 that the tool searches for events on Yelp. The tool name reinforces this. However, it does not elaborate on what specific event data is returned or how it differs from related tools like yelp_search_businesses, but the core purpose is unambiguous.

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 is provided on when to use this tool versus alternatives such as yelp_search_businesses or yelp_get_business. The description does not include any context about prerequisites, filters, or typical use cases.

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