WhatsApp Business accounts and numbers

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

Annotations cover read-only/idempotent/non-destructive, but the description adds substantial non-annotation context: unreadable portfolios are reported rather than dropped, only accounts shared with this profile are reachable, WABAs without numbers cannot send, and billing is 0 Hermoso credits because Meta bills directly. That is real behavioral disclosure beyond the structured fields.

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?

Information-dense with each paragraph carrying distinct facts (quality rating, unreachable accounts, duplicate display names, sharing scope, credits, prerequisite), and the key 'Start here' guidance is near the front. However, the heavy ALL-CAPS emphasis makes it longer and noisier than it needs to be.

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 no output schema, the description carries the return-value burden and does so: it explains that accounts, ids, display names and quality ratings come back, and that unreadable portfolios are reported. Nothing an agent needs to call 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?

Zero parameters, so the baseline is 4 and the schema fully covers the (empty) surface. The description mentions wabaId being optional, but that parameter belongs to other WhatsApp tools rather than this one, so it adds little meaning here.

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?

States a precise verb+resource: the WhatsApp Business accounts shared with this profile and the phone numbers on each, plus the ids other WhatsApp tools need. It self-identifies as the entry point ('Start here') and is clearly separable from siblings like list_connector_accounts and set_connector_accounts, which it references.

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?

Gives explicit when-to-use ('Start here'), prerequisites ('Needs Meta connected'), the failure mode when nothing is ticked, the special case when exactly one account is ticked (wabaId optional), and names the alternative tool (set_connector_accounts) that controls which accounts are visible.

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