remove_contacts_bulk

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

No annotations provided, and the description only marks it as a 'mutation' but does not disclose destructive nature, reversibility, permissions needed, or side effects (e.g., what happens if list_id is invalid).

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?

Single sentence with clear action and resource. No unnecessary words; includes [mutation] hint. Efficient and front-loaded.

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?

Missing details on return behavior (e.g., success/failure counting), idempotency, and edge cases (e.g., non-existent contact IDs). With no output schema, description should compensate but does not.

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?

Input schema has 100% description coverage, so description adds no extra meaning. Baseline 3 is appropriate as the schema already documents each parameter.

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 tool removes multiple contacts from a marketing list, with the explicit verb 'Eliminar' (delete) and resource 'contactos en bloque' (bulk contacts). It distinguishes from the sibling 'remove_contact_from_list' by implying bulk 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?

No guidance on when to use this tool versus alternatives like 'remove_contact_from_list' for single contacts. The description lacks context about prerequisites or exclusions.

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