delete_workspace_invitation

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description correctly aligns with them. It adds valuable context beyond annotations by specifying 'permanently delete' and 'pending' — clarifying that only pending invitations are affected, which is a meaningful behavioral constraint an agent must know before calling.

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 two concise sentences, with the primary purpose front-loaded in the first sentence and a targeted parameter hint in the second. There is no filler, and every word contributes to operational clarity, making it highly efficient for an agent to parse quickly.

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 destructive operation with annotations covering the safety profile and a likely simple output, the description is mostly sufficient. However, the missing explanation for invitation_id is a notable gap that could hinder correct invocation, and there is no mention of error behavior or idempotency. Given the tool's simplicity, the definition is adequate but not fully 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 description coverage is 0%, so the description must compensate for both parameters. It explains workspace_id with a helpful reference to list_workspaces(), but invitation_id is left completely unexplained — no guidance on how to obtain it, its format, or its role. With only one of two parameters covered, the description fails to fully compensate for the schema's lack of detail.

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 the action ('Cancel and permanently delete') and the resource ('a pending workspace invitation'), which distinguishes it from sibling tools like delete_invitation that target general invitations. The verb+resource combination is specific and unambiguous, making the tool's purpose immediately obvious to an agent.

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 does not explicitly mention when to use this tool versus alternatives such as delete_invitation or update_workspace_invitation. It does provide a hint on how to obtain workspace_id via list_workspaces(), which is useful for invocation, but lacks any explicit when-to-use or when-not-to-use guidance, leaving the selection partially to inference.

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