search_events

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and does not mention pagination, default behavior, response format, rate limits, or requirements. The description is too minimal to convey how the tool behaves beyond 'searching'.

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 with no filler words or repetition. It is front-loaded with the action and resource. However, it is not as information-dense as it could be, relying on generic phrasing, so it doesn't earn a 5.

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's complexity (8 parameters, nested object, no output schema, no annotations), the description is inadequate. It doesn't mention what results look like, how pagination works, or any important operational details. The description adds only a basic purpose, leaving agents without crucial context.

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 description coverage is high (88%), so parameters are already well-documented in the schema. The description's 'various criteria' adds no specific parameter meaning. Baseline 3 applies since the schema does the heavy lifting.

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 a search action over Eventbrite events with filtering criteria, which distinguishes it from siblings like get_event (single event retrieval), get_categories, and get_venue. The phrase 'various criteria' is somewhat generic but the overall purpose is clear and distinct.

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?

Usage is implied by 'Search' - the tool is for finding events matching criteria, but there is no explicit guidance about when to use it vs alternatives or exclusions. No sibling tools are referenced, leaving the agent to infer context.

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