fetchEvents

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

The readOnlyHint annotation already marks this as a safe read operation. The description adds useful context about events grouping markets and optional keyword search, going beyond the annotation. No contradictions with annotations.

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 two short, purposeful sentences. The first sentence delivers the core action, and the second provides essential context. No filler or redundant 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?

The description provides a high-level understanding of events and keyword search, but for a tool with 14 parameters and no output schema, it lacks details on pagination behavior, sorting defaults, or return structure. It is adequate but not fully complete for complex use cases.

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%, so the descriptions in the schema already document all 14 parameters adequately. The description adds a bit of context (e.g., grouping markets) but does not significantly enhance understanding of individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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 action ('Fetch events') and the resource ('events'), and provides a concrete example explaining what an event is (grouping related markets). This distinguishes it from sibling tools like 'fetchEvent' (singular) and 'fetchEventsPaginated' (paginated).

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 implicitly suggests use for keyword-based search and explains events' nature, but it does not explicitly specify when to use this tool over alternatives like 'fetchEvent' for a single event or 'fetchEventsPaginated' for pagination. No when-not-to-use or exclusion criteria are provided.

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