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

Annotations already declare non-read-only, destructive and open-world, so the description adds real value beyond that: the 14-day validity, e-mail versus returned link delivery, role-scoped visibility, owner-only authorisation, and the preview/confirm protocol with the requirement of explicit consent. These are traits an agent could not infer from the annotations alone.

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 purpose and the two role scopes are front-loaded, followed by delivery mode, ownership and the confirmation protocol. It is dense but well ordered; a few clauses duplicate what the schema fields already say, which keeps it just below top marks.

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?

With four well-documented params and no output schema, the description covers permissions, delivery, role semantics, expiry and the safety protocol. It never says what the preview contains or whether the returned link can be re-retrieved, which is a minor remaining gap.

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%, so the schema already explains nom, role, email and confirmer in detail; the description largely restates the same role and e-mail semantics. Baseline 3 applies, with only the owner-assignment aside as marginally new information.

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 states a specific verb and resource: creating a personal invitation valid for 14 days, with the two role options and the two delivery modes named. An agent can tell it apart from siblings such as annuler_invitation, changer_role_membre or lister_equipe without opening the schema.

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?

It clearly states the prerequisite (owner only), the out-of-scope case (naming an owner happens in the app), and the two-step workflow: preview with confirmer=false, then act with confirmer=true only after explicit consent. It does not point to the sibling used to cancel or list invitations, so the alternative routing is not complete.

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