search_events

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

With no annotations, the description carries the full burden for behavioral disclosure. It usefully conveys that the operation is a read-only search scoped to public events, but it does not mention pagination/continuation behavior, rate limits, authentication needs, or result ordering. This is adequate but has clear gaps.

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?

One short sentence, with no filler, with the core search purpose and criteria front-loaded. It is appropriately concise, though it sacrifices the opportunity to mention the continuation parameter or alternative tools.

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?

For a search tool with four optional parameters and an output schema, the description covers the essential purpose and three key parameter semantics. It is incomplete around the continuation parameter and provides no guidance on how search results differ from organization-scoped event endpoints, but it is reasonably usable as-is.

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?

The description maps three of the four parameters to meaningful concepts: q to keyword, location_address to location, and location_within to distance. However, schema description coverage is 0%, and the continuation parameter is left completely unexplained, so the description only partially compensates for the schema gap.

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 the verb 'search' with the resource 'public events' and the main criteria: keyword, location, or distance. It differentiates from organization-scoped siblings like search_organization_events_by_date through the word 'public, but it does not explicitly name any sibling or edge case that would rule out confusion.

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 description implies when to use the tool: when an agent needs to find public events by free-text or geographic criteria. It does not provide explicit when-not guidance or name alternatives, such as list_organization_events for organization-scoped searches.

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