Get an Etix event/performance by id

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by stating 'Read-only, no Etix account required,' which is not covered by annotations, and by detailing the exact data returned. With no output schema, this description fully carries the burden of telling the agent what to expect.

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?

A single, information-dense sentence that leads with the core purpose and then enumerates the return payload. Every clause contributes to agent understanding; there is no fluff or redundancy.

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?

For a single-parameter, read-only tool with no output schema, the description is complete: it specifies the input, the source of that input, the full set of returned data, and the access prerequisites (no account). An agent has everything needed to call 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?

Schema coverage is 100%, and the event_id parameter is fully described in the schema (type, example, and source 'From etix_search'). The description reinforces this by calling it 'numeric event_id' and reiterating the source, but adds no new information beyond what the schema already 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?

States a specific verb ('Fetch') and resource ('single Etix event/performance') by its numeric event_id, and enumerates the returned fields (name, date/time, venue, organizer, price range, offer levels). This clearly differentiates it from sibling etix_search (search) and etix_get_venue (venue lookup).

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?

Explicitly tells the agent to get the event_id from etix_search, establishing a clear workflow dependency. It also notes that it is read-only and requires no Etix account, which guides when to use it. However, it does not explicitly state when not to use it or name alternative tools for other use cases, leaving some inference.

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