whatsapp_admin

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

No annotations provided, so description carries full burden. It lists actions and token requirement but lacks details on side effects (e.g., destructuring of delete_user), rate limits, or auth specifics beyond token.

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?

Description is brief and front-loaded with purpose. However, listing action values inline could be more scannable. No redundant sentences.

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?

With 0% schema coverage and no annotations, the description fails to fully explain all four parameters. It doesn't describe return values (though output schema exists) or the effects of each action beyond their names.

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 0%, so description must explain parameters. It explains action values and token requirement but leaves 'name' and 'confirmed' undefined. These parameters are crucial for actions like create_user or delete_user.

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?

Description clearly states it handles admin operations and lists specific actions like list_users, create_user, delete_user, enable_history. This distinguishes it from sibling WhatsApp tools which focus on messaging, media, etc.

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?

Mentions requirement of admin token, which is a key prerequisite. However, no explicit guidance on when to use this tool versus alternatives; sibling tool names imply context, but description could be clearer.

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