List Event Attendees

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description goes beyond them by disclosing that pagination is bounded and that 'every page counts against the API quota' – a real rate/quota trait not present in the structured data. It stops short of noting auth/credential needs, which the schema partially hints at via 'account'.

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?

Three short, front-loaded sentences with no filler; the quota constraint is stated compactly. The only inefficiency is the redundant first sentence that repeats the title instead of leading with substantive information.

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 100% schema coverage and annotations covering safety, the description supplies the key operational caveat (quota-consuming paging). With no output schema, the return shape (attendee fields, continuation state) is only partially implied via the schema's max_items note, a minor omission.

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 schema already documents all six parameters, including the quota/continuation semantics of all_pages and max_items. The description adds only the quota reminder for all_pages, marginally reinforcing but not extending schema meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The first sentence verbatim restates the tool title/name ('List Event Attendees'), which is tautological. 'Reads community data' adds a mild read-vs-write signal distinguishing it from create_event_attendee/delete_event_attendee, but it offers no differentiation from the many other list_* siblings. The purpose is inferable mainly from the name, not the description.

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 never says when to use this tool versus alternatives like get_event, list_events, or search_member, nor any prerequisite. The only usage-flavored content is a pagination note ('bounded all_pages'), which is about mechanics rather than selection. No when/when-not guidance exists.

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