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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the returned content (check-in status and basic profile), the attendee pools controlled by source, and the required authorization scope. The precise return shape is only vaguely described, but the essential invocation behavior is transparent.

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?

The description is two focused sentences: the first front-loads the core purpose, and the second adds source options and the auth prerequisite. There is no filler, repetition, or unnecessary 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?

For a list operation with no annotations and no output schema, the description covers purpose, auth, and source semantics, while the schema covers all parameters. The main remaining gap is the precise return-object shape, but the phrase 'check-in status and basic profile' plus rich parameter documentation is enough for an agent to call it correctly.

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?

The input schema already documents all six parameters with 100% coverage, so the baseline is 3. The description adds real semantic value by explaining that source='rsvp' maps to free RSVPs and source='ticket' to paid ticket purchases, which the bare enum does not convey. The remaining parameters are sufficiently covered by 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?

The description uses a specific verb ('List') and resource ('an event's attendees') and adds 'with check-in status and basic profile', making the operation's scope clear. It does not explicitly name or exclude a sibling such as hivelearn_list_event_waitlist, so differentiation from that tool is implied rather than stated.

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 concrete selection guidance for the source parameter ('rsvp' for free RSVPs, 'ticket' for paid ticket purchases) and states the required read:events scope. It does not mention exclusions or alternatives, but the usage context is clear enough for an agent to choose the right source.

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