delete_invite

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds nothing on top of that — it doesn't say whether deletion revokes a pending invitation, whether it fails for unknown emails, or whether it is scoped to a workspace, so there is no value beyond the structured fields.

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 words, front-loaded and waste-free, with the verb leading. It is efficient, though the terseness edges toward under-specification rather than genuine concision.

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 one-parameter delete whose annotations already carry the destructive/idempotent profile and with no output schema required, a minimal description could suffice. However, it omits invocation context and the effect of deletion on the invitation lifecycle, leaving gaps an agent would need filled before calling it confidently.

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 100% (the single 'email' parameter is documented in the schema as 'The email of the customer'). The description adds no syntax, format, or scoping meaning beyond that, so the baseline 3 for full schema coverage applies.

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?

Names a specific verb and resource ('Delete ... Invitation'), which sets it apart from reads, but it is essentially an expansion of the tool name/title 'delete_invite'/'Delete Invite'. It gives no scope detail (whose invitation, pending vs. accepted) and does not distinguish itself from nearby tools like remove_member or invite_user, so it is only minimally clearer than the identifier.

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 offers no when-to-use guidance, no prerequisites (e.g. ownership or admin requirement), and no mention of alternatives such as remove_member or invite_users_bulk. The agent must infer everything about invocation context.

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