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

Annotations already declare readOnlyHint=true, and the description adds the concrete endpoint mapping (GET /events/{event_id}/orders/ vs GET /organizations/{organization_id}/orders/) plus the field set returned. It does not describe pagination flow (only the schema's continuation field does), so it is good but not exhaustive.

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 tight sentences: scope and returned fields first, the parameter rule second. Zero filler, fully front-loaded.

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 list tool with no output schema, it covers scope, returned fields, and the identifier rule; pagination and expansions are handled by the schema. Nothing critical is missing, though a note on pagination expectations 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 coverage is 100% so the baseline would be 3, but the description adds the mutually-exclusive constraint between event_id and organization_id that the schema does not express, plus the notion of scope per identifier. The remaining params (expand, status, continuation, changed_since) are left to the schema.

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 (List) and resource (orders) with two clearly delineated scopes: one event vs. all events of an organization. It also enumerates the returned fields (buyer name/email, status, costs) and maps to the exact REST endpoints, making it easy to distinguish from the singular eventbrite_get_order sibling.

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 directive 'Pass exactly one of event_id / organization_id' is a crisp, actionable rule that tells the agent which parameter shape selects which scope. It lacks an explicit pointer to alternatives such as eventbrite_get_order for a single order, so it falls just short of a full when/when-not treatment.

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