sauvegarder_serveur

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

With no annotations, the description must carry the full burden. It does disclose key behavior: the operation is read-only with respect to Discord and does not capture full message history. It omits where the backup is stored, whether existing backups are overwritten, permission prerequisites, and what the call returns.

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?

Two short, front-loaded sentences with zero filler. The scope statement comes first and the limitation clause second, so an agent can parse it instantly.

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 one-optional-parameter tool this is close to sufficient, but with no annotations and no output schema the description should say where the snapshot lands and what the response contains. The behavioral scope is well covered; the mechanics are not.

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% and the description never mentions the single 'nom' parameter. The default value ('Sauvegarde manuelle') implies it is a label, but the description adds no meaning about its purpose, format, or effect on the stored backup.

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 gives a specific verb and resource: 'Créer une sauvegarde locale de la structure actuelle (salons, rôles, paramètres)'. This clearly distinguishes a local configuration snapshot from mutating siblings like modifier_salon or preparer_restauration. No explicit sibling is named, so it stops short of a 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?

'Aucun changement Discord, aucun historique intégral de messages' signals what the tool is NOT for, which implicitly steers agents away from expecting message archives or Discord-side mutations. However, no alternative tool is named and there is no explicit 'use this when you want X' condition.

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