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 mentions 'returns up to 10 matching results,' which provides useful limit information, but it does not disclose other behaviors such as pagination, sorting, or search scope (e.g., only current events vs. historical).

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 that efficiently conveys the core purpose and key constraint. Every part is meaningful, and there is no superfluous information.

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 low complexity (one parameter, no output schema, no annotations), the description covers the essential purpose and a behavioral constraint (result limit). However, it lacks details on search behavior, such as whether it searches across all events or only certain fields, and does not describe the return format.

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 coverage is 100% (one parameter with description). The description adds value by specifying that the query can be 'by team name or text query,' which provides context beyond the schema's generic 'Search term' description. It helps the agent understand the search scope.

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 that the tool searches events by team name or text query, which distinguishes it from sibling tools like get_events (which lists all events) and get_live_events (which filters by live status). The verb 'search' and resource 'events' are specific and unambiguous.

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 usage for searching when you have a query, but it does not explicitly state when to use this tool versus alternatives. It lacks guidance on when not to use it or mention of sibling tools for different scenarios.

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