eb_org_attendees

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

Annotations provide readOnlyHint=true, so safety is covered. The description adds the 'organizer side' qualifier, hinting at access scope, but doesn't elaborate on pagination, response format, or any rate limits. It's consistent with annotations but provides minimal extra behavior.

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?

One concise sentence that front-loads the function. No wasted words.

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 simple read-only list tool with a well-described schema and readOnlyHint, the description is adequate. It doesn't explain the return format, but the name 'List attendees' implies a list. Given low complexity, it's complete enough.

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 covers all parameters with clear descriptions: org_id from eb_my_organizations, status filter enum, continuation token. The description itself adds no additional param detail, but schema coverage is 100%, 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?

Description clearly states the action (List), the resource (attendees), and the scope (across an organization's events, organizer side). This differentiates from eb_event_attendees which lists attendees for a single event.

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 description gives clear context for when to use this tool: when you need attendee lists at the organization level, not per-event. While it doesn't explicitly mention alternatives, the scope is specific enough to guide selection. No exclusions are stated, but the 'organizer side' indicates a privilege requirement.

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