add_guest

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

Annotations only include destructiveHint: false, with no readOnlyHint or other safety metadata. The description adds the structural detail that a guest group is a household, but it does not disclose side effects such as duplicate handling, how plus-one fields fit into the household, or what the response contains. For a create operation with minimal annotations, this is insufficient.

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?

A single, front-loaded sentence with no filler. Every word earns its place, and the key distinction (guest group/household) is included without redundant 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?

With 7 parameters, no output schema, and minimal annotations, the description is too sparse to be complete. It doesn't state return values, error conditions, or how this tool relates to other guest list operations, though the schema does cover parameter semantics.

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 describes all 7 parameters at 100% coverage, so the baseline is 3. The description adds no additional parameter-level meaning beyond the household concept, and it doesn't highlight the required first_name/last_name or the affiliation default.

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 clear verb ('Add') with a specific resource ('guest group (household)') and target ('guest list'). The parenthetical clarifies that this creates a household rather than an individual guest, which helps differentiate it from related guest tools, though it doesn't explicitly name any sibling alternatives.

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?

No guidance is given about when to use this tool versus alternatives like invite_guest_to_event, set_event_guests, or update_guest_address. There are no prerequisites, exclusions, or context cues beyond the name and description, so an agent must infer the intended usage scenario.

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