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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds useful behavioral context by disclosing that the response includes check-in history and swap history, which the annotations do not cover, though it says nothing about error behavior for invalid/missing 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 compact sentences, front-loaded with the purpose and payload contents, with the endpoint mapping appended. Every clause carries information and nothing is repeated from the schema.

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 read-only single-resource fetch with full schema coverage and annotations covering the safety profile, the description supplies the missing piece: what extra data the ticket payload carries. It is nearly complete, though a note on the split-region lookup (why override_location exists) would round it out.

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 the schema already documents event_id, ticket_id formats and the override_location enum semantics. The description adds no parameter-level detail beyond the endpoint template, 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 (one ticket of an event) and clarifies scope as a single ticket, which distinguishes it from the sibling humanitix_list_tickets. The description also names the payload's distinguishing content (check-in history, swap history) and the underlying REST endpoint.

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?

Usage is only implied: needing a single ticket's detail rather than a ticket list. No explicit when-to-use/when-not statement, no named alternative (e.g., humanitix_list_tickets) and no prerequisites such as required IDs being valid for the caller's region.

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