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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the description's job is to add context — and it does: it discloses the payload contents (destination plus the 20 most recent deliveries) and, importantly, that the secret is not returned ('sans secret'), which matters for security-sensitive handling. The admin prerequisite and the bounded 20-delivery window are also real behavioral facts. It does not say what happens on an unknown id or whether deliveries are paginated.

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?

A single compact sentence with the audience constraint front-loaded and no filler; every clause carries information. It is close to optimal for a read tool, though the mixed French/English phrasing adds a small parsing cost for an English-context agent.

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 no output schema, the description usefully sketches the return shape (destination plus last 20 deliveries, secret excluded) and the admin gate. But for a tool whose only input is an opaque 32-character id, the omission of what that id refers to and of failure behavior leaves a meaningful 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?

There is one required parameter, `id`, with 0% schema description coverage, so the description carries the full explanatory burden — yet it never says what the id identifies. Given the sibling set, an agent cannot tell whether it is a payment page id, a webhook id, or a delivery id, nor is the 32-hex format hinted at.

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 names a concrete verb (lire) and a concrete resource (the Pay webhook's destination plus its last 20 deliveries), which is far more specific than the bare title. It implicitly separates itself from configure_payment_page_webhook and retry_payment_page_webhook by describing a read of delivery history, but it never names those siblings 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 leading 'Administrateur :' signals that this is an admin-only read, which is useful usage context. However, there is no explicit statement of when to reach for this versus retry_payment_page_webhook (to re-send a failed delivery), configure_payment_page_webhook (to change the destination), or describe_payment_pages, leaving routing to inference.

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