eventbrite_search_events

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

No annotations are provided, and the description does not disclose any behavioral traits such as authentication requirements (despite the api_key parameter), rate limits, or what happens when the search returns no results. The agent has no insight into the tool's behavior beyond the fact that it searches.

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 severely under-informative. It does not earn its place because it repeats the name of the tool without adding value. An effective description would provide context beyond the name.

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 4 parameters with no schema descriptions, no output schema, and no annotations, the description is grossly incomplete. It fails to provide any guidance on usage, parameter semantics, or expected behavior, leaving the agent with significant ambiguity.

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 0% (no parameter descriptions), and the description does not explain any of the four parameters (q, location_address, start_date_range_start, api_key). The agent receives no guidance on required format, optionality, or meaning of each parameter.

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 'Search for events on Eventbrite' clearly states the verb (search) and resource (events on Eventbrite). It distinguishes the tool from siblings like eventbrite_get_event (single event retrieval) and eventbrite_create_event (creation). However, it lacks specificity about the search criteria (keyword, location, date) which are evident from the schema but not mentioned.

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. Sibling tools like eventbrite_get_event or eventbrite_get_attendees have different purposes, but the description does not indicate the appropriate context for searching versus retrieving specific events or attendee lists.

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