set_event_guests

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

The description discloses idempotency, the effect of invited:true/false on each group, and that only listed groups are affected. Annotations only provide destructiveHint:false, so the description adds significant behavioral context beyond annotations, fully addressing agent decision needs.

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 four concise sentences, front-loaded with the purpose and followed by key details. No superfluous information; every sentence earns its place, making it efficient and easy to parse.

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?

Given no output schema, the description is largely complete for a setter tool—it explains behavior and usage. However, it lacks any mention of return values (e.g., confirmation or error handling), which would make it more complete for agents expecting to process results. Still, it covers the core aspects well.

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%, but the description adds critical meaning: it explains that invited:true 'ensures every guest in the group is invited' and invited:false 'removes the invitation', and clarifies that guest_groups only affects listed groups. It also mentions event_id comes from list_events, adding value beyond 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 clearly states the verb 'Set' and resource 'guest groups invited to an event' with '(bulk)'. It distinguishes from siblings like invite_guest_to_event (individual) and remove_event_invitation, making the tool's specific purpose unambiguous.

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 provides context: 'Use this to assign guests to events in bulk (e.g. by tier/affiliation/location)' and notes that other events' invitations are preserved. It implies appropriate use for bulk group operations but does not explicitly mention when not to use it or name alternative tools like invite_guest_to_event, which would strengthen guidance.

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