delete_invitation

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

The description explicitly states 'permanently delete', which conveys irreversibility and aligns with the destructiveHint annotation. It also specifies the target is a 'pending invitation', giving clear behavioral expectations. It does not mention potential errors or required permissions, but the core behavior is well described.

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 extremely concise, consisting of two short sentences with no redundant wording. The workspace_id hint is integrated efficiently.

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?

The description covers the core action and one parameter hint but omits information about return values, error conditions, or relationship to sibling invitation-deletion tools. Given the output schema exists, some context is still missing for a fully self-contained 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?

Only workspace_id receives any explanation; the purpose of hub_profile_id and invitation_id is not described. Since all three parameters are required, the lack of descriptions for two of them leaves significant semantic gaps.

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 identifies the action as canceling and permanently deleting a pending invitation, which is specific and unambiguous. However, it does not distinguish this from the sibling 'delete_workspace_invitation' tool, leaving a slight ambiguity about invitation scope.

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?

No guidance is provided on when to use this tool versus alternatives, nor does it mention prerequisites or side effects. The only hint is pointing to list_workspaces() for workspace_id, which is useful but insufficient.

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