remove_unsubscribed_bulk

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

The description adds only '[mutation]' which is redundant given the tool name implies deletion. With no annotations, it fails to disclose behavioral traits such as irreversibility, required permissions, or impact on related data.

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 extremely short (two lines), which is concise but lacks structure and front-loading of critical information. It omits important details like the operation's destructive nature.

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 the complexity of bulk deletion (6 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain return values, confirmation steps, or scope boundaries beyond what's in the schema.

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 the description adds no additional meaning. The parameters are well-documented in the schema, meeting the baseline for this dimension.

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' (delete) and resource 'bajas' (unsubscribes) with 'en bloque' (in bulk), making the tool's purpose specific and distinguishable from siblings like 'remove_contacts_bulk' which targets 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?

No guidance on when to use this tool versus alternatives like 'remove_from_blacklist' or 'remove_whatsapp_optout'. It does not specify context such as prerequisites or when not to use bulk deletion.

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