yelp_search_events

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds nothing beyond them — no mention of what the Yelp API returns, authentication expectations for api_key, rate limits, or whether start_date is an epoch timestamp. For an external API tool it is thin.

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?

A single short sentence is efficient but under-specified rather than concise; it spends its only words restating the tool name instead of adding usable detail.

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?

With no output schema, no annotations about return shape, no required params and four undocumented params, an agent cannot confidently construct a call. The description leaves essentially all invocation-relevant details unspecified.

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?

Four parameters with 0% schema description coverage and no parameter explanation in the description. Notably start_date is typed as a number while the others are strings, and nothing anywhere clarifies the expected format (epoch seconds? millis?) or how categories is encoded — a real invocation hazard.

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?

States a specific verb (search) and resource (events) scoped to Yelp, which implicitly separates it from yelp_search_businesses and yelp_get_reviews. It stops short of explicitly naming what distinguishes it from other event-search siblings like tm_search_events or seatgeek_search_events.

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?

There is no guidance on when to use this versus yelp_search_businesses, yelp_autocomplete, or the several other event search tools in the sibling list. The agent must infer usage purely from the tool name.

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