user_invitations_delete

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

With no annotations provided, the description carries the full burden. It clearly indicates the action is destructive ('delete/cancel') and describes the return value. However, it does not mention prerequisites (e.g., invitation must be pending), side effects, or permission requirements, which would provide fuller transparency.

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 compact and well-structured: a short verb phrase, an Args section, and a Returns section. No wasted words, and the format is easily scannable for an agent.

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 simple delete operation with one parameter and an output schema, the description covers the essential aspects: what it does, the parameter meaning, and the resulting confirmation. It is sufficiently complete, though a note about which invitations can be cancelled would have made it fully comprehensive.

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 only specifies the parameter name and type with 0% description coverage. The description compensates fully by explaining that 'invitation_id' is 'The ID of the invitation to cancel', giving the parameter clear semantic meaning 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 a specific action ('Cancel/delete a user invitation') with a specific resource ('a user invitation'). It distinguishes itself from sibling user_invitation tools by indicating this operation removes an invitation, as opposed to listing, getting, or creating.

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 purpose is clear enough that an agent would know to use this tool when cancelling/removing a user invitation. It does not explicitly list alternative tools or exclusions, but the context and explicit verb provide clear situational guidance.

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