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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine value beyond that by disclosing the response contents (attendee, registration, release, answers, tags, amounts paid) and the underlying API call, which tells the agent how heavy the fetch is. It stops short of noting error behavior for missing/unauthorized tickets.

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 dense sentences, front-loaded with the primary action and scope, then the endpoint reference. No filler, no 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?

With no output schema, the description usefully compensates by naming the data returned, and the schema fully covers the optional account_slug fallback. Slightly incomplete on error/permission behavior, but sufficient for an agent 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 description coverage is 100%, so all three parameters are already documented in the schema, including the account_slug fallback to TITO_ACCOUNT and the ti_... slug format. The description's 'by slug (ti_...)' merely echoes 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?

States a specific verb ('Fetch') and resource ('a single ticket by slug'), and enumerates the expanded associations returned (attendee, registration, release, answers, tags, amounts paid), which clearly separates it from the sibling tito_list_tickets. The API endpoint mapping (GET /:account/:event/tickets/:ticket_slug) reinforces the exact scope.

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?

Implied usage is clear from 'single ticket by slug' versus the list sibling, but the description never explicitly states when to use this over tito_list_tickets or tito_get_registration, nor any prerequisites. Adequate but with a clear routing gap.

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