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

readOnlyHint=true already establishes the safety profile, so the description's remaining burden is modest. It adds useful context by disclosing the payload shape and that releases are embedded in the response, but says nothing about auth requirements, error behavior for unknown slugs, or whether live/test events differ in output.

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, zero filler, and the core action is front-loaded before the field enumeration. The trailing 'Tito: GET /:account/:event' is compact and useful for mapping to the upstream API.

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 no output schema, the description compensates by naming the fields returned, including the nested releases. Parameters are self-documenting via the schema and annotations cover read-only safety. Minor gap: nothing on failure modes for an invalid slug or on the live/test_mode distinction for callers.

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 description coverage is 100%, so both event_slug and account_slug are already fully explained (including the URL-position convention and the TITO_ACCOUNT fallback). The description's 'by slug' adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ('Fetch a single event by slug') with the identifying key named, plus an enumeration of the returned payload (title, dates, location, currency, live/test_mode, releases). This cleanly distinguishes it from the sibling tito_list_events and from tito_get_release/tito_get_ticket, which fetch adjacent resources rather than the event itself.

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 'by slug' phrasing implies when this tool applies, but there is no explicit when-to-use/when-not, and no pointer to alternatives (e.g. use tito_list_events to discover slugs). The one contextual hint — that tito_whoami lists reachable accounts — lives in the schema for account_slug, not in the description.

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