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

With no annotations, the description carries the full behavioral burden. It correctly discloses the most important trait, 'No link is created,' and implies an approval-gated workflow, but it does not mention permission requirements, return behavior, or other execution context.

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?

Three short sentences, no repetition, and useful information is front-loaded. Each sentence adds a distinct point: purpose, side-effect guarantee, and sequencing.

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 zero-parameter preview tool with no output schema, the description covers the essential purpose, side effect, and workflow step. It could be stronger by clarifying what 'explain' returns or how it relates to list_whatsapp_accounts, but it is complete enough to call correctly.

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 tool has zero parameters and the schema is empty, so there are no parameter semantics to explain. The baseline for zero-param tools is 4, and the description does not introduce misleading parameter expectations.

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 states a specific preview action: explain what connecting a WhatsApp number does, list already-connected accounts, and explicitly say no link is created. It distinguishes itself from connect_whatsapp_account, though it does not mention the sibling list_whatsapp_accounts even though this tool also lists accounts.

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 gives clear sequencing guidance: call this first, then connect_whatsapp_account after user approval. The condition is explicit enough to know this is a prerequisite step, but it does not state when to prefer list_whatsapp_accounts or any exclusions.

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