remove_contact_from_list

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

The description tags the tool as '[mutation]' indicating state modification, but lacks annotations and does not disclose side effects, error conditions, or whether the contact must exist in the list. No contradictions with annotations (none provided).

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 description is a single sentence with a dash and a mutation tag, conveying essential information without excess. It is front-loaded with the action, though could benefit from minor structuring.

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 one-parameter tool, the description is mostly adequate but lacks clarity about which list the contact is removed from. It states 'de una lista de marketing' but does not specify if the list is implicit or how it is determined, leaving ambiguity.

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 baseline is 3. The description repeats the schema's parameter description ('ID del contacto a eliminar') without adding context beyond the schema. No extra semantics are provided.

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 the verb ('eliminar' / remove) and the resource ('contacto de una lista de marketing'), specifying that it removes an individual contact from a marketing list. This distinguishes it from siblings like 'remove_contacts_bulk' which operates on multiple contacts.

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 provides no guidance on when to use this tool versus alternatives such as 'remove_contacts_bulk' or 'remove_unsubscribed_bulk'. It does not specify prerequisites or contexts where individual removal is preferred over bulk operations.

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