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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, but not the operational constraints. The description adds quota/availability behavior ('Gratuit, sans quota, toujours ouvert') that the annotations do not convey, which is genuinely useful for deciding whether to spend a call on feedback. It does not describe what the tool returns or where the feedback goes.

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?

The trigger condition is usefully front-loaded, but the availability idea is stated twice ('Gratuit, sans quota, toujours ouvert' and 'reste disponible même hors fenêtre gratuite'), and the cryptic 'N'utilise aucune unité' adds noise without clear meaning. Roughly a third of the text is redundant or unclear.

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 feedback tool with no output schema and annotations that already cover the safety profile, the description supplies when-to-use, acceptable content, and availability. A brief note on whether a confirmation is returned would fully close the gap, but nothing essential is missing.

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 coverage is 100% and the message parameter already carries a description, so the baseline is 3. The description goes beyond it by enumerating the acceptable content categories (tool remark, calculation, feature idea, bug), clarifying what belongs in 'message' rather than merely restating 'Votre retour, en clair'.

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 and resource ('Envoyer un retour / suggestion pour améliorer l'application Synergieloc') and enumerates the kinds of feedback accepted (tool remark, calculation, feature idea, bug). No sibling tool in the list performs feedback submission, so the agent can identify it unambiguously.

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 opening 'QUAND un résultat vous semble faux, incomplet, ou qu'un endpoint plante' states explicit trigger conditions for when to call it, and the 'remarque sur un outil, un calcul, une idée de fonctionnalité, un bug' clause covers the full range of valid scenarios. Availability is stated ('toujours ouvert ... même hors fenêtre gratuite'), leaving no inference required.

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