Supprimer un(e) contact

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

Annotations already declare destructiveHint=true; description adds 'Action irréversible' and notes confirmation elicitation—useful context beyond annotations. No contradictions.

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?

Description is short and to the point: purpose, warning, and parameter. Could be slightly more structured (e.g., bullet points), but no unnecessary words.

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?

Adequate for a simple delete tool with output schema present. Covers the action, irreversibility, parameter. Could mention return behavior (e.g., success/error response), but not essential.

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% with a clear description of 'id' as numeric unique identifier. Tool description repeats parameter info but adds no new meaning beyond schema. Baseline 3 applies.

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?

Description clearly states 'Supprime un(e) contact de BoondManager', a specific verb and resource. Sibling tools include create, get, update, search, etc., so this stands out as the delete operation.

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?

Description mentions irreversibility and confirmation elicitation, but does not explicitly state when to use this tool over alternatives like boond_contacts_search (to find the contact first) or boond_contacts_get (to verify before deletion). Implicit usage is clear for deletion.

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