remove_whatsapp_profile_picture

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

The description adds the [mutation] tag and confirmation requirement beyond the schema. But with no annotations, it fails to disclose permissions, reversibility, or response format, leaving behavioral gaps.

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?

Two sentences, front-loaded with the action and key condition. No wasted words.

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 mutation tool with 2 parameters and no output schema, the description covers the core purpose and the confirmation safeguard. It could mention that removal is per session and permanent, but is otherwise adequate.

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 base score is 3. The description reinforces the confirm parameter's role but adds no new meaning beyond what the schema already provides for session_id.

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 action ('Eliminar foto de perfil') and the resource ('de WhatsApp', 'de una sesion'). It distinguishes from siblings like 'update_whatsapp_profile' and 'get_whatsapp_profile' by specifying removal.

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?

It explicitly requires confirmation ('pasar confirm=true para ejecutar'), which informs the agent that the tool should not be called without the confirm flag. However, it does not contrast with alternative tools or specify when not to use it.

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