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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are covered structurally. The description adds content-level context that annotations cannot: it discloses that the return is field definitions plus configuration examples. It does not mention auth/prerequisite requirements, permissions on the external form, or whether config examples are static or live-derived.

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?

One sentence, front-loaded with the verb and resource, zero filler. The only nit is that it is written in French while the rest of the tool surface (titles, sibling names) is English, a minor consistency cost rather than a length problem.

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 zero-parameter, read-only tool with no output schema, the description carries the main remaining burden: telling the agent what comes back, which it does (fields and configuration examples). Given the simplicity of the tool and the annotation coverage, that is nearly enough, though it could have clarified the return against describe_forms and list_form_webhooks.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. Nothing in the sentence misleadingly implies inputs are required.

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 sentence pairs a clear verb ("Lire" / read) with a specific resource ("champs et exemples de configuration des formulaires externes"), so the agent knows this returns schema/field definitions and config examples rather than a list of existing webhooks. It does not distinguish itself from close siblings such as list_form_webhooks or describe_forms, which is what keeps it at 4 rather than 5.

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?

"avant création" implies the usage context: call this before create_form_webhook to learn the expected fields. However, it never explicitly names create_form_webhook or any alternative, nor does it say when NOT to use it (e.g., to inspect already-configured webhooks, which list_form_webhooks appears to cover). Usage is implied rather than stated.

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