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

Discloses internal mechanism (uses removerPaciente and resolves id/link from fresh list) and reiterates irreversibility. Annotations already signal destructiveness, so description adds useful behavioral context without contradiction.

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 sentences, no redundancy. First sentence states core purpose and mechanism, second adds bulk support. Information is front-loaded and every word adds value.

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 delete tool, covers permanence, irreversibility, mechanism, and bulk mode. Lacks mention of cascading effects on related data (e.g., consultations), but overall adequate for typical use.

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?

Adds meaning for patient_id (primary identifier) and patient_ids (bulk support), but does not explain the 'account' parameter. Schema has 0% description coverage, so the description partially compensates but leaves one parameter unspecified.

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?

Clearly states it permanently deletes a WebDiet patient, using specific verb 'delete' and resource 'patient', and distinguishes from sibling tools like create or list by emphasizing irreversibility and bulk support.

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 warns that the action is irreversible, implying caution, and mentions bulk support for batched execution. However, it lacks explicit guidance on when to use this tool versus alternatives like update or get.

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