androidapi_relink_whatsapp_account

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

The description adds that it re-generates the QR code, which is a behavioral detail. Annotations already indicate non-readOnly (write) and non-destructive, so the description provides moderate additional context but does not detail side effects like invalidating old QR.

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, direct sentence that conveys the essential purpose without any extraneous words or details.

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?

The description covers purpose and usage context, but does not explain the return value (e.g., whether the QR code is returned directly or as a URL). Since there is no output schema, the description should compensate.

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% with clear parameter descriptions. The tool description does not add semantic value beyond what is already in the schema; it only mentions the action (re-generate QR).

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 re-generates QR code to reconnect an existing disconnected WhatsApp account. It distinguishes itself from the sibling tool 'androidapi_link_whatsapp_account' which would handle new account linking.

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 specifies the tool is for reconnecting a disconnected account, implying it should not be used for new accounts. However, it does not explicitly mention when not to use or provide alternative tool names.

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