invitations_delete

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

No annotations are provided, so the description carries full disclosure burden. It clearly states the destructive effect (token immediately invalidated and cannot be used) and the limitation (cannot cancel accepted invitations). For a delete operation with no annotations, this is solid behavioral disclosure.

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?

Three concise sentences, zero waste. Covers purpose, immediate effect, and limitation without redundancy.

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 single-parameter delete operation with no output schema, the description is adequate. It covers the intent, the destructive effect, and the boundary condition. It could optionally note whether the operation is idempotent or what happens when trying to cancel a nonexistent invitation, but for a single-parameter operation this is reasonably complete.

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% with the uuid parameter already described as 'Invitation UUID to cancel.' The description reinforces that this is a cancellation of a pending invitation, adding the semantic context that the uuid refers to a pending invitation's token. The description adds some value by clarifying the token's lifecycle behavior, though the schema alone largely covers the parameter meaning.

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?

Clear specific verb (cancel/delete) + resource (invitation). States the token is immediately invalidated, which distinguishes it from other invitation tools like invitations_list, invitations_create, and invitations_resend. The effect (invalidating the token) is explicit.

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 clearly states the tool is for pending invitations and explicitly notes it cannot cancel already-accepted invitations. However, it does not name the alternative for handling accepted invitations (which likely shouldn't be cancellable at all), nor does it distinguish when to use this vs invitations_resend. The context of 'cancel a pending invitation' is clear but no sibling exclusion is explicitly stated.

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