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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that the returned payload includes a snapshot of the questions as they existed at submission time, which is non-obvious. It says nothing about what "version actuelle" means operationally (optimistic concurrency? revision pointer?) or about errors when the id is stale.

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 dense sentence with the read action front-loaded and the return payload appended after the semicolon. No filler, though the semicolon clause packs three ideas together and slightly obscures the versioning point.

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 read-only tool with no output schema, the description does indicate the shape of the return (entered data plus a question snapshot), which is the main thing needed. It remains incomplete on the two opaque parameters and on what the "current version" is used for, which matters because the tool is explicitly positioned as a pre-modification step.

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%, so the description carries the full burden for the two required parameters — yet it never explains what "id" identifies or what the string parameter "response" is (a response identifier, a slug, a token). With a 64-char bounded string and an exclusiveMinimum integer, an agent has no textual basis to construct either value.

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 specific verb ("Lire") and resource ("une réponse") plus an ancillary payload ("sa version actuelle", entered data, question snapshot), so the operation is identifiable. However, it does not distinguish itself from close siblings such as list_form_responses, get_contact_form_responses, list_form_submissions or update_form_response, leaving the agent to infer scope from the name alone.

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 modification" implies the usage context — read the record before editing it — which is genuine when-to-use guidance rather than nothing. It stops short of naming the alternative tool (update_form_response) or stating exclusions, so the routing decision remains partly inferred.

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