list_event_invitees

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'List invitees' but does not mention pagination, filtering, ordering, permissions, error behavior, or the structure of the returned list. For a read operation, it lacks context about what the agent should expect in terms of response and side effects.

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 a single concise sentence that is front-loaded with the action and resource. It contains no filler or redundancy, making it highly efficient.

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?

Although the schema covers all parameters, there is no output schema and no annotation. The description is too minimal to fully contextualize the tool: it does not state what the returned invitee list looks like, how pagination works, or any filtering/prerequisite details. Given the simple nature of the tool, more elaboration on return values and behavior would be expected.

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 100%, and each parameter (count, email, status, event_uuid) has its own description. The tool description itself adds no parameter-level meaning, but since the schema fully documents them, the baseline of 3 is appropriate.

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 'List invitees for a specific event' uses a specific verb (List) and resource (invitees for an event), clearly distinguishing it from siblings like list_events or get_event by scoping to invitees of a particular event. It directly states the tool's function without ambiguity.

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 implies usage when you need invitees of a particular event, but it does not explicitly mention when not to use it or provide alternatives among the sibling tools. There is no exclusionary guidance, so the context is only implicitly derived from the purpose.

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