update_whatsapp_session

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

No annotations are provided, so the description must cover behavioral traits. It includes a [mutation] tag indicating state change but does not disclose side effects, required permissions, or rate limits. For a mutation tool, more detail is expected.

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 concise, with a single sentence plus an example and a [mutation] tag. It is front-loaded with the core purpose and contains no unnecessary words or redundancy.

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 only 2 parameters, no output schema, and no annotations, the description adequately covers the purpose and input semantics. It references a related tool (get_whatsapp_status) for obtaining IDs, which adds context. For a simple update tool, it is sufficiently complete.

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 the schema already documents both parameters. The description adds context (e.g., 'max 50 caracteres' is in schema, 'Null para quitar la etiqueta' is also in schema). It does not add significant extra meaning beyond the schema, so baseline 3 is appropriate.

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 that the tool edits a WhatsApp session by updating its label (name), with a specific verb 'Actualiza' and resource 'sesion de WhatsApp'. The example 'Soporte', 'Ventas' indicates typical use cases, distinguishing it from other session operations like connecting or deleting.

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 a use case example (identifying numbers) but no explicit guidance on when to use this tool versus alternatives like get_whatsapp_status or connect_whatsapp. The instruction 'Usa get_whatsapp_status para obtener los IDs' gives a prerequisite but not exclusions.

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