wrike_delete_invitation

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

With no annotations, the description carries the full burden of behavioral disclosure. While 'delete' implies a destructive action, it does not mention consequences, reversibility, permissions, or side effects. The description is too sparse to provide meaningful transparency beyond the bare operation.

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 a single, short phrase: 'Cancel/delete an invitation'. It contains zero filler words and is front-loaded with the core action. It is as concise as possible for a simple delete operation.

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 tool without annotations or output schema, the description adequately states the action but leaves out contextual details such as whether the invitation must be pending, what happens after deletion, or any prerequisites. It is minimally viable but lacks depth.

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 schema has 100% coverage with 'Invitation ID (required)' clearly describing the only parameter. The tool description adds no additional parameter semantics, but the baseline is 3 because schema coverage is high. No further explanation is needed.

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 'Cancel/delete an invitation' clearly states the action (cancel/delete) and the resource (invitation), making it distinct from sibling tools like wrike_delete_attachment or wrike_delete_comment. It is specific, unambiguous, and immediately understandable.

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?

There is no guidance on when to use this tool versus alternatives such as wrike_list_invitations or wrike_invite_user. The description only states the action, offering no contextual information about prerequisites or scenarios, so it fails to guide the agent in tool selection.

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