relink_whatsapp

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

With no annotations, the description carries full burden. It discloses credential deletion and cache preservation, but does not fully describe side effects (e.g., service interruption until re-link) or auth requirements. It is adequate but not thorough.

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, no wasted words. First sentence states purpose, second sentence details output and usage. Perfectly front-loaded.

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's simplicity (1 optional param, no output schema, no annotations), the description covers operation and user instructions well. Missing only explanation of 'waitMs' and explicit relation to siblings. Nearly 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?

The schema has 0% description coverage and one optional parameter 'waitMs' (default 25000). The description does not explain this parameter at all, leaving the agent to guess its purpose (likely QR wait time). This is a significant gap.

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's purpose: 'Delete stale credentials and start a fresh QR pair.' It uses specific verbs ('delete', 'start') and resources ('credentials', 'QR pair'), and distinguishes from siblings like 'wait_for_link' which handles the subsequent step.

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 when to use the tool: when credentials are stale and need refreshing. It provides explicit instructions for rendering the QR and user action. However, it does not explicitly state when not to use it or mention alternatives beyond the implied sibling 'wait_for_link'.

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