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

The description goes well beyond the annotations, detailing permanent deletion on drafts, archiving on published invitations, invite links stopping, guest counts and RSVP totals dropping, host restoration on the website, phone-guest allowance behavior, and lack of guest notification. No annotation is contradicted; in fact, the description reinforces the destructiveHint.

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 front-loaded with the primary use case and then packs high-value behavioral details, source guidance, and an exclusion into a compact set of sentences. Every sentence earns its place, and there is no redundant restatement of the tool name or title.

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 the destructive nature, the tool supplies all necessary side effects (deletion vs. archive, counts, restoration, phone allowance, notification), a source for IDs, and an explicit alternative for a related but different action. An output schema exists, so return-value details are not required in the description.

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 baseline is 3. The description adds meaningful provenance for invitation_ids by instructing callers to get them from lemonvite_list_guests, and it explains the consequence that removed guests' invite links stop working, enriching the schema's 'these guests are removed' note.

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 states a specific verb ('remove') and resource ('guests from a Lemonvite invitation'), and it differentiates from the sibling lemonvite_update_guests by explicitly warning not to use removal for detail fixes. It also clarifies the draft vs. published distinction, making the tool's purpose unmistakable.

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?

It opens with an explicit when-to-use trigger ('Use this when the user wants guests taken off'), tells the caller where to source invitation_ids ('from lemonvite_list_guests'), and names the alternative tool for fixing details (lemonvite_update_guests). This leaves no ambiguity about when it applies versus its siblings.

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