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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still earns credit by disclosing a real behavioral caveat beyond the annotations: absent fields mean never populated, and an empty profile may mean WhatsApp did not answer — an ambiguity the agent must not misread as missing data.

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 sentences, front-loaded with purpose and field list, then usage ordering, then the empty/missing caveat. Dense and purposeful, though the field enumeration makes the opening clause long.

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?

No output schema exists, and the description compensates by naming every returned field plus the failure-ambiguity case. For a single-parameter read tool with annotations covering safety, there is nothing material an agent needs that 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?

There is only one parameter and schema coverage is 100%, with the schema itself noting the id comes from list_accounts and that other networks are rejected. The description reinforces scoping ('one WhatsApp Business account') but adds no new syntax or format detail, so the baseline of 3 applies.

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 specific verb and resource ('Read the business profile ... on one WhatsApp Business account') and enumerates the exact fields returned (about, description, email, websites, address, vertical, profile picture URL). This clearly separates it from update_whatsapp_profile and from the many other WhatsApp tools (flows, templates) in the sibling list.

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?

Explicitly gives a usage condition: read this before calling update_whatsapp_profile, which only changes the fields passed. That tells the agent the read-then-write pattern. It does not state when-not to use it or name a competing read tool, so it falls short of a 5.

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