Supprimer une absence

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

Annotations already set destructiveHint=true. The description adds 'Action irreversible' which provides extra context that the action cannot be undone, going beyond the annotation. However, no other behavioral details like cascading effects or authorization needs are disclosed.

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?

Extremely concise: two short sentences. First sentence states the action, second emphasizes irreversibility. Every word 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?

For a simple delete tool with one parameter, annotations, and an output schema (available but not shown), the description covers what it does and the key consequence (irreversible). No missing critical information.

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 100%, so baseline is 3. The description does not mention the 'id' parameter, but the schema already describes it with pattern and description, so no added meaning needed.

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 'Supprime une absence de BoondManager' (deletes an absence from BoondManager), specifying the verb (supprime) and resource (absence). It distinguishes from sibling tools like create, get, search, update.

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 description only says 'Action irreversible' which hints at consequences but does not explicitly guide when to use (e.g., only when certain that absence should be permanently removed) or when not to use (e.g., use update instead to modify). No alternatives mentioned.

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