fetchEvent

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

Annotations already declare readOnlyHint=true, so the tool is safe. The description adds that it returns a single result or throws EventNotFound, which is behavioral insight beyond annotations. No contradictions.

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?

Two sentences with no waste. The first sentence states purpose, the second adds behavioral detail and relationship to sibling. Front-loaded and efficient.

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?

With 14 parameters and no output schema, the description is minimal. It does not explain how to ensure a single result (e.g., use eventId or slug, avoid pagination params) or describe the return format. Schema descriptions fill some gaps but the description lacks guidance for effective use.

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 each parameter has a description. The description adds overall context but does not clarify which parameters are relevant for single-event lookup (e.g., eventId, slug vs. limit, cursor). 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 'Fetch a single event by lookup parameters', which is a specific verb+resource. It distinguishes from siblings like fetchEvents (multiple) and fetchEventsPaginated (paginated) by emphasizing single result and throws on not found.

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 indicates this is a convenience wrapper for fetchEvents when expecting a single result, but does not explicitly state when not to use it or alternatives. The sibling list helps but guidance is implied rather than explicit.

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