tm_search_events

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

The description states 'Search' implying read-only, but no annotations exist. It fails to disclose that an api_key parameter is required for authentication, which is critical for usage. No rate limits, side effects, or other behavioral traits are mentioned.

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, which is concise but severely under-specified. It does not front-load essential information and fails to earn its place by providing value 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 7 parameters, no output schema, and no annotations, the description is grossly incomplete. It offers no context for expected inputs, outputs, or usage scenarios, leaving the agent with minimal information.

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?

With 0% schema description coverage, the description adds no meaning to the 7 parameters. It does not explain what 'keyword', 'city', 'countryCode', etc., represent, leaving the agent without guidance for correct invocation.

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 Ticketmaster' is almost a tautology, restating the tool name without adding specificity. It does not differentiate from sibling tools like seatgeek_search_events or tm_search_attractions, and fails to convey the scope of search parameters.

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, nor any conditions or exclusions. The description lacks any context for appropriate usage.

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