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

The annotations declare the tool as destructive and not idempotent, and the description adds real context beyond them: owner-only authorization, the concrete effect (the invitation link stops working), and a two-step confirmation protocol that must wait for the user's explicit consent. That is exactly the extra behavioral guidance annotations cannot carry.

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?

It is three compact clauses. The effect and the precondition are front-loaded, the authorization constraint follows, and the confirm protocol comes last. No sentence is wasted.

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 two-parameter destructive tool with full schema coverage and no output schema, the description covers effect, authorization, and safety flow adequately. It omits what happens if the invitation was already used, such as the error behavior, which would round out the picture.

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%, and both parameters are already documented in the schema, including the confirmer preview semantics. The description restates the confirmer=false/true behavior but adds no syntax or format detail beyond that, so it is at the baseline.

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 pairs a specific verb with its resource and adds a limiting condition: canceling an invitation that has not yet been used, and that the link stops working. This distinguishes the tool in practice from inviter_membre, retirer_membre, and lister_equipe, even though no sibling is named explicitly.

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 states a clear usage context: it is reserved for the owner, it applies only to unused invitations, and it lays out the preview-then-act flow with confirmer. It does not explicitly compare itself with the alternatives or state what to do when an invitation has already been used, which stops it short of a 5.

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