get_unsubscribed_list

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

With no annotations, the description carries full burden but only states the tool 'obtiene la lista'. It does not disclose behavioral traits such as read-only nature, pagination behavior, rate limits, or whether it clears filters. The schema's 'page' parameter implies pagination, but the description does not confirm this.

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, concise sentence that front-loads the purpose ('Ver contactos dados de baja'). It is efficient with no wasted words, though it could benefit from breaking into two sentences for clarity.

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 tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It does not mention pagination, date filtering, or result format. For a list tool with many siblings, more contextual guidance is needed to fully inform the agent.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. Each parameter is already documented in the schema, so the description does not compensate or enrich.

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 retrieves a list of contacts who have unsubscribed from mass mailings, using a specific verb ('Obtiene') and resource ('contactos dados de baja'). It distinguishes from sibling tools like 'list_whatsapp_optout' by specifying the context of mass mailings, though it does not explicitly differentiate.

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 (e.g., 'list_whatsapp_optout' for WhatsApp opt-outs) or when not to use it. It implies usage for viewing unsubscribed contacts but lacks explicit context or exclusion criteria.

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