eventbrite_get_attendees

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds nothing beyond that: no word on pagination of attendee lists, result limits, authentication requirements for the api_key parameter, or whether attendee PII is returned.

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 short sentence with no filler, front-loaded with the action. It is efficient, though that efficiency comes partly from omitting almost all useful detail.

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 and 0% parameter coverage, the description should explain what attendee records contain, how pagination works, and how credentials are supplied. None of that is present, leaving the agent to guess at the shape and limits of the response.

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% for both parameters. The phrase 'for an Eventbrite event' hints that event_id identifies the event, but the api_key parameter (authentication) is entirely undocumented and no format details are given, so the description does not compensate for the coverage gap.

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?

It states a verb and resource ('Get attendees') but essentially restates the tool name, adding only that the event is an Eventbrite event. With siblings like eventbrite_get_event and eventbrite_search_events in the namespace, the description does nothing to distinguish scope (e.g., attendee list vs. single attendee vs. event details).

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?

There is no guidance on when to use this versus eventbrite_get_event or eventbrite_search_events, and no mention of prerequisites such as needing an event_id or valid API credentials. Usage is only inferable from the name and required parameter.

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