precheck_delete_whatsapp_session

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

The description reveals the tool is a pre-check that shows affected settings and alternative sessions. It states the precondition (disconnected state) but does not explicitly state that it is non-destructive; the name 'precheck' implies safety.

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, front-loads the main purpose, and includes an important note. It is structured but could be slightly more organized with bullet points.

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 single parameter, no output schema, and no annotations, the description covers purpose, preconditions, and what it shows. It could clarify the output format (list of affected items), but is largely complete for a pre-check tool.

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?

Only one parameter (session_id) with schema coverage 100%. The description adds no extra meaning beyond the schema description, so baseline score of 3 applies.

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 starts with 'Pre-verificar eliminación de sesión WhatsApp' and clearly states it shows affected configurations and alternative sessions, distinguishing it from the actual deletion tool.

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 includes an important note that only disconnected sessions can be deleted and instructs to disconnect first if connected. It implicitly advises against using this for actual deletion, but could explicitly mention the sibling 'delete_whatsapp_session'.

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