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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description still adds genuine context: only the currently public version is returned (so drafts/unpublished states are excluded), visit status and partnership presence are surfaced, and the published signature is explicitly distinct from interviewed persons' identities. That is meaningful behavioral disclosure beyond the annotations.

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 sentences with no filler, so it is not bloated. However it is not front-loaded on the action: the first sentence describes output content before the reader knows what the tool does, which weakens scannability.

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 read-only tool with no output schema, the description helpfully covers most of what comes back, which is real value. What is missing is any statement of the identifying input (slug) and any routing versus the sibling search tool, leaving the definition adequate but not complete.

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 two parameters. The description covers the meaning of 'langue' ('dans la langue demandée') but the allowed values already sit in the schema enum, and it says nothing about the required 'slug' parameter or its format. It compensates only partially for the missing schema documentation.

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 is a noun phrase describing the returned artifact ('Version actuellement publique de l'article dans la langue demandée') rather than stating the action of fetching one article. It never says the article is identified by slug, and it does not differentiate itself from the sibling rechercher_articles_carnet, which also concerns Carnet articles. An agent can infer the purpose from the title plus this text, but the description alone is only adequate.

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?

There is no guidance on when to use this versus rechercher_articles_carnet or any other sibling. With nine siblings including a clearly overlapping article-search tool, the absence of routing guidance is a real gap. Only an implicit 'retrieve one thing' reading distinguishes it.

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