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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial behavior: what is excluded, the newest-first/unknown-last ordering, that limit caps ticket records (1-500), that newestOrderComplete and coverageNote signal missing dates or incomplete scans, and that totalIsExact governs summary counts. This is information an agent cannot get from schema or annotations.

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?

Purpose and permissions are front-loaded, and nearly every clause carries real information. The single dense paragraph becomes a run-on in the middle (ordering, flags, and counts packed together), but there is little outright waste.

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?

No output schema exists, so the description must describe returns — and it does, naming fields, per-source totals, check-in count, and the flags that qualify data reliability. Permissions, ordering, and multiplicity ('multiple tickets can belong to one person') are all covered, leaving nothing an agent needs unstated.

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?

With schema description coverage at 0%, the description compensates fully: limit's semantics ('selects latest N ticket records (1-500)'), the allowed source values, category as a filter, include_staff as the staff gate, and event_id as required. It adds meaning beyond the bare schema types.

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+resource ('List guests at an event you manage') and enumerates the ticket data returned (name, email, phone, category, plus-ones, source, check-in). It implicitly separates itself from data-poor siblings like get_guest_details, but never names an alternative such as list_visible_attendees, so differentiation is inferential rather than explicit.

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?

Gives concrete preconditions ('Requires event_id; you must be a host') and scoping rules (cancelled/refunded excluded, staff only via include_staff), which tell the agent when the tool's output is the right one. It stops short of naming sibling tools or stating exclusion conditions for choosing them.

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