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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower; the description still adds real context beyond them: a required confirmation step, Plus-plan gating on some module deletions, and the unusual non-delete behavior of the friendship entity (unfriend or cancel/decline a request). The confirmation and plan-gating details are the kind of thing an agent cannot infer from annotations.

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 destructive warning is front-loaded, which is good, but the parent_id clause is a long run-on with grammatical errors ("de le contact", "de le projet") and an awkwardly worded closing sentence about Plus-plan modules whose referent is 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?

There is no output schema, so the description must carry return expectations, which it does implicitly by stating deletion is permanent. For a three-parameter destructive tool the essential safety and parent_id semantics are present, though the partial parent_id mapping and vague plan-gating sentence leave small 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 schema itself defers parent_id meaning to the description ("voir la description"), and the description supplies the per-entity mapping of what parent_id refers to. The list covers only seven entities out of roughly forty enum values, so an agent deleting a nested entity such as learning_session or maintenance_log gets no guidance.

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 opens with a specific verb and irreversibility claim ("Supprimer définitivement un élément, sans retour possible") and identifies the entity-type parameter as the selector. It does not explicitly contrast with the sibling dandori_delete_task, which likely overlaps for the 'task' entity, so it falls short of full sibling differentiation.

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?

It gives one useful procedural rule (ask for confirmation before deleting) and notes that deletions in Plus-plan modules require that plan, plus the special friendship semantics. It never says when to prefer this generic tool over the entity-specific delete sibling, so routing guidance is only implied.

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