whatsapp_numbers_write

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

Annotations already declare destructiveHint, openWorldHint, and non-idempotency, and the description adds action-specific behavior: removing stops the AI answering, update_display_name is reviewed by Meta, and reassign moves the number within the workspace. It does not cover auth requirements or response behavior, so it is strong but not exhaustive.

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 front-loaded and dense, with no wasted sentences. The pipe-delimited action list is efficient but slightly harder to scan than separate lines, which keeps it from a 5.

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 destructive mutation tool with no output schema, the description covers the key actions, their effects, and required inputs. It could say more about success responses or permission requirements, but nothing essential for invoking it correctly is missing.

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?

With 71% schema coverage, the schema already documents most parameters, and the description adds important action-to-parameter mappings for newAgentId, displayName, and enabled. It does not describe agentId or fully explain phoneId beyond the schema, but it adds meaningful semantics.

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 names the resource (a connected WhatsApp number), enumerates the exact operations (remove, reassign, update_display_name, set_voice_calling), and explicitly distinguishes connection from the sibling tool create_channel_connect_link. An agent can identify the tool's scope without opening the schema.

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 a clear alternative for connecting a new number and a precondition to confirm before remove. It does not explicitly route the agent to whatsapp_numbers_read for listing or update_whatsapp_number_settings for other settings, but usage is clear from the action list.

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