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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavior beyond them: cancelled/refunded tickets are excluded, staff are omitted unless include_staff is set, host-level authorization is required, and the result is a downloadable link rather than inline data.

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 front-loaded sentence that opens with the verb and resource before piling on clauses; the column list and exclusion rules all earn their place. Minor waste remains in restating 'Read-only' and 'Requires event_id', which annotations and the required-array already assert.

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 supplies the return shape (download link plus named columns) and covers authorization, filtering, default exclusions, and every parameter. An agent has everything needed to call it correctly without opening the schema.

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 0%, so the description carries the burden and does explain all three parameters: event_id is required, category is an optional filter, and include_staff toggles staff records. It never states accepted category values or the maxLength constraints, so semantics are good but not exhaustive.

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 ('Export a live event's guest list ... as a downloadable CSV ... return a download link') with the exact record types (free RSVPs, guest-list adds, comps, paid tickets) and output columns enumerated. It does not name a sibling to contrast with, so an agent must infer the split from list_guests/get_guest_details/export_form_responses_csv 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?

Gives clear selecting context: requires event_id, you must be a host, there is an optional category filter, and staff appear only with include_staff. No exclusions or explicit 'use X instead when Y' alternative routing is offered, so the agent still has to reason about CSV export vs the list_guests/get_guest_details siblings.

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