bulk_add_to_blacklist

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

No annotations are provided, so the description must disclose behavioral traits. It only marks the operation as a mutation but does not address idempotency, error handling, authorization requirements, or effects on existing blacklist entries.

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 clear sentence that conveys the purpose without unnecessary words. It could benefit from bullet points but remains appropriately sized.

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 and no annotations, the description does not explain return values, success indicators, or error cases. This leaves the agent without enough information to correctly handle the response.

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 description adds no additional meaning beyond the schema's field names and types. No examples or constraints are given for 'phones' or 'reason'.

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 it adds multiple phone numbers to a blacklist specifically for mass marketing. The verb 'Añadir' is specific, and the '[mutation]' tag confirms the operation. It distinguishes from the sibling 'add_to_blacklist' which implies single addition.

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 implies bulk usage by including 'múltiples' and 'varios', and the sibling 'add_to_blacklist' exists for single additions. However, it lacks explicit guidance on when not to use it or alternatives beyond the name.

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