delete_contact

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

The description warns about irreversibility ('OPERACIÓN IRREVERSIBLE — el contacto se elimina permanentemente'), which is critical behavioral info. However, it does not cover other behavioral aspects like authentication requirements, side effects, or error handling. With no annotations, the description partially fulfills the transparency burden.

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, each earning its place: first states the action, second highlights irreversibility and required inputs. No fluff, front-loaded essential information.

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?

Given no output schema, the description is silent on return values or success/failure indicators. It also does not mention idempotency or behavior for non-existent contacts. For a delete tool, basic completeness is adequate but could be expanded.

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%, so the schema already documents all parameters. The description mentions only the two required parameters (list_key and number), which matches the schema but adds no extra meaning beyond what the schema provides. The optional email parameter is omitted from the description.

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 'Elimina un contacto de una agenda' (deletes a contact from an agenda), providing a specific verb and resource. It distinguishes this tool from siblings like add_contact or update_contact by emphasizing deletion and irreversibility.

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 explicitly states when to use the tool (to delete a contact) and lists required inputs (list_key and phone number). It does not explicitly exclude alternative scenarios, but the context from sibling tools makes the usage clear.

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