Envoyer un mail

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

Even without annotations, the description transparently discloses the irreversible, immediate nature of the action: 'action sortante et définitive : le mail part'. This fully informs the agent of the tool's side effect.

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?

Concise two-sentence description with front-loaded key action ('ENVOIE immédiatement') and no unnecessary words. Each sentence serves a purpose: action, usage guidance, and parameter hint.

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 simple send-email tool with no output schema and well-covered parameters, the description is complete. It covers irrevocability, alternative for draft, multi-recipients, and account requirement for sender. No critical gaps.

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%, but the description adds value by noting that 'expediteur' must correspond to an account, referencing a related tool 'lister_comptes'. Other parameters are adequately described in the schema, and the description reinforces the comma-separated list for recipients.

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 clearly states the tool sends an email immediately, using strong verbs 'ENVOIE immédiatement' and differentiating from the sibling 'creer_brouillon' which prepares a draft. The purpose is unambiguous.

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?

Explicitly instructs to use only when the user truly wants to send, and provides a direct alternative ('creer_brouillon') for previewing. Also notes that multiple recipients are allowed, separated by commas.

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