eb_search_events

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds behavioral context: this is an unofficial consumer search absent from the documented API, supports various filters, and compact mode returns slim results. It also gives a prerequisite (resolve place first), going beyond the baseline expectation.

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?

Three concise sentences, each delivering essential information: purpose, prerequisite, and filter/compact guidance. No filler or repetition, and the key points are 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?

With 14 parameters and no output schema, the description covers the key invocation strategy: place resolution, filter groupings, and compact mode. It omits `aggs` and detailed pagination, but the high schema coverage and annotations compensate sufficiently 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 high at 86%, so the baseline is 3. The description enhances this by grouping parameters into filter categories (keyword, dates, category/format ids, free/paid, online-only) and points to eb_reference for ID values. It also explains compact's purpose for browsing/ranking, adding useful conceptual structure 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 opens with 'Search public Eventbrite events', clearly specifying the verb and resource. It further distinguishes this from the documented API's absence, setting it apart from sibling tools like eb_org_events and eb_venue_events which operate on org-specific data.

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?

It provides clear usage context: it is the consumer search, and it tells the agent to first resolve the location via eb_resolve_place. It references eb_reference for IDs and suggests compact=true for browsing/ranking. It does not explicitly list exclusions or alternative tools, but the framing implies when to use it.

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