search_events

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds mild context by stating the output is 'factual' metadata with listed prices, but it does not disclose pagination, result-size limits, or date-filter behavior beyond the schema defaults.

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 front-loaded sentence with no filler. Every word contributes to identifying the resource and the nature of the returned data.

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?

The description is adequate for a minimal keyword-only invocation, and the output schema covers return values. However, with many optional filter parameters and no parameter descriptions in the schema, an agent gets no guidance on using location, date, radius, or classification filters.

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 0%, so the description should compensate for the 10 parameters, but it does not mention any input semantics beyond the overall search concept. Parameter names and enums in the schema are self-explanatory, but date formats, radius-unit behavior, and classification values are left undocumented.

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 states a specific verb ('Search') and resource ('live events'), and clarifies the return contents: event, venue, date, and listed-price metadata. It is clearly distinct from hotel, flight, and vehicle search siblings, though it does not explicitly name an alternative.

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?

The usage context is implied by the resource name: an agent needing live event data should use this tool. However, there is no explicit guidance about when not to use it or how it compares to related search tools.

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