Create AddEvent RSVP Attendee

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

Beyond the annotations, the description discloses critical behavioral traits: default silent creation when notify is omitted, the uniqueness requirement for email per event, and error conditions (400 for duplicate email or missing rsvp_form_data fields). It also states the return value clearly. These details add substantial value over the minimal annotation set and do not contradict any hint.

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 well-structured with clear sections (overview, Args, Returns, Examples, Error Handling) and uses bullet points for parameters. It is thorough but not verbose; every sentence contributes either context, example, or error information. This makes it easy to scan and process.

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 create operation with 5 parameters, a nested object, and no output schema, this description covers all necessary aspects: purpose, prerequisites, every parameter, return value, error handling, and usage examples. It is fully actionable for an agent to invoke the tool correctly and understand the outcome.

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 parameters. The description adds practical context, such as the 'backfilling attendees from another system' use case for omitting notify and the note that the default RSVP form requires a 'name' field. This enriches parameter understanding beyond the raw schema definitions, though most semantic weight is carried 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 opens with 'Registers an RSVP attendee on an event,' which uses a specific verb and resource, clearly distinguishing it from sibling tools like search_rsvps, get_rsvp, update_rsvp, and delete_rsvp. It further clarifies scope by stating it only works on events created with rsvp_enabled: true, removing any ambiguity about applicability.

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 explicit when-to-use and when-not-to-use guidance: 'Don't use when: the event doesn't have RSVP enabled (check with addevent_get_event first).' It also gives concrete examples of appropriate usage, such as adding an attendee or importing signups silently, making it easy for an agent to decide when to invoke this tool.

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