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

The annotations say readOnlyHint=false and destructiveHint=false, and the description importantly adds that the call 'Remplace et invalide le lien précédent' — a side effect that the annotations do not convey and that sits in tension with destructiveHint=false, since a previously working link is silently killed. The added 'ne pas publier la réponse' warning also implies the response contains a secret URL. Beyond these two facts the description says nothing about permissions, rate limits, or whether the new link can be recovered later, so the disclosure is valuable but thin.

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?

Two short sentences, both front-loaded: the action first, then the side effect and the sensitivity warning. Every clause carries operational weight and there is no filler.

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 mutation with no output schema, the description covers the two things an agent most needs to know: the previous link is invalidated, and the result must not be exposed. It still leaves the parameter's meaning and the required permissions unexplained, which is a real gap for a write tool that produces a credential.

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 0% for the single required parameter 'id', and the description never says what that id identifies — a community member, a workspace, or something else. With one parameter and no schema prose, the description is the only place this could be clarified, and it is not. Only the exclusiveMinimum: 0 constraint in the schema hints at the shape.

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?

States a specific verb and resource in 'Générer un lien d'accès privé', which is clearer than the title alone because it names the artifact produced. It does not, however, distinguish this from the other access-link creators in the sibling list (create_affiliate_access_link, create_enrollment_access_link, get_telegram_invite_link), so the agent must infer that this one is scoped to community members from the tool name only. The description is also in a different language than the tool name, which adds friction.

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?

'ne pas publier la réponse' gives a concrete handling instruction for the result, which is genuine usage guidance. There is no statement of when to prefer this over the sibling access-link tools, nor any precondition such as the member needing to exist or the caller needing a given permission. Usage is implied rather than routed.

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