formulaires_lire

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output context (questions, choices, response link) but says nothing about behavior on an unknown or invalid formulaire_id, nor about permissions on restricted forms.

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 front-loaded sentence that identifies the subject and enumerates the returned content with no filler. Every clause of the description earns its place.

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, which is a real contribution. However, for a lookup-by-id tool it omits how to obtain the id (presumably from formulaires_lister) and what happens on a missing form, leaving 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?

Schema description coverage is 0%, so the schema gives only a bare unsigned integer named formulaire_id. The description never mentions the parameter, where the id comes from, or its expected form, so it fails to compensate for the coverage gap.

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?

Names the resource (un formulaire) and states the operation is retrieving its detail, enumerating what the detail contains (description, questions, choix, lien de réponse). This contrasts with the sibling formulaires_lister, which lists rather than details, though the sibling is never named 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?

There is no when-to-use, when-not-to-use, or alternative routing. Nothing tells the agent to call formulaires_lister first to obtain an id, or to prefer this tool over the listing tool when the user wants a single form's content.

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