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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries real weight by disclosing that this call replaces and invalidates the previous link — a side effect an agent would not otherwise predict. It also implies the response contains a secret that must not be published. Missing are permission requirements and whether the old link's revocation is immediate.

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 with no filler, and the replacement warning is front-loaded before the publication caution. The description is in French while the rest of the tool surface is English, which is a minor consistency cost but not padding.

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?

There is no output schema, and the description partially compensates by warning that the response is sensitive. For a one-parameter mutation that silently revokes a prior link, though, the missing identification of what 'id' refers to leaves a real gap before an agent can call it safely.

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 single parameter 'id' has 0% schema description coverage, so the description must compensate and does not — it never says whether 'id' is an affiliate, user, or workspace identifier. The agent must guess the target of the link from the tool name alone.

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 ('Générer un lien d'accès privé'), but never says what the link grants access to — the affiliate is only identifiable from the tool name. With three near-identical siblings in the list (create_community_member_access_link, create_enrollment_access_link, get_telegram_invite_link), the description provides no differentiation between them.

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' is a real usage instruction (do not surface the returned link), which is more than most tools offer. However, there is no statement of when to prefer this tool over the sibling link-creation tools, no prerequisites, and no note on what happens if a link already exists beyond the replacement warning.

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