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

Annotations already provide destructiveHint=true and idempotentHint=true, so the description has lighter burden. It adds genuine transparency by disclosing that removed guests' invite links stop working, reinforcing what removal actually does.

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 three short sentences with no filler. It front-loads the use condition, then gives a behavioral consequence and a parameter source, so every sentence earns its place.

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 two-parameter destructive tool with annotations and an output schema, the description covers when to use, what happens to invite links, and how to find the needed identifiers. It lacks only fuller coverage of event_id and explicit alternative routing to sibling tools.

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?

With schema description coverage at 0%, the description must compensate for parameter meaning. It explains that invitation_ids can be found via lemonvite_list_guests, but it does not explain event_id beyond a general reference to a Lemonvite invitation.

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 that this tool removes one or more guests from a Lemonvite invitation and explicitly notes that removed guests' invite links stop working. It distinguishes the intent from sibling tools like add_guests and update_guests by emphasizing 'actually removed'.

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 gives a direct trigger condition: use when the user wants guests actually removed. It also routes to lemonvite_list_guests to find the required invitation_ids. It does not explicitly warn against using this for non-removal updates, but the condition is clear.

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