tm_search_events

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the API source ('Ticketmaster') and does not disclose any behavior beyond annotations, such as the need for an api_key, pagination behavior, rate limits, or what the results contain. With annotations carrying the burden, this is a minimal contribution.

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 extremely short, but this is under-specification rather than conciseness. It is front-loaded and has no wasted words, but for a tool with seven undocumented parameters and many alternatives, a single six-word sentence does not earn its place as an adequate definition.

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 (seven parameters, zero schema descriptions, no output schema), the description is wholly inadequate. It says nothing about parameters, authentication, result shape, or how this differs from the numerous other event-search tools, leaving the agent without the information needed to invoke it correctly.

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 schema has seven parameters with 0% description coverage, and the description mentions none of them. Parameters such as api_key, size, startDateTime, and classificationName are completely undocumented, so the agent gets no semantic guidance for any input field.

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 gives a clear verb+resource ('Search for events') and names the source ('on Ticketmaster'), so the purpose is immediately understandable. However, it does not distinguish this tool from sibling event search tools such as seatgeek_search_events, eventbrite_search_events, or yelp_search_events, leaving the agent to infer differentiation from the name alone.

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?

There is no guidance on when to use this tool versus its many sibling event-search tools, nor any mention of prerequisites, typical use cases, or exclusions. The only implied usage is that it searches events, which is already obvious from the name.

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