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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: permission requirements, free-business restriction, and the need to validate access. This goes beyond annotations without contradicting them.

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 clear and front-loaded with purpose, followed by usage guidelines. It contains five sentences, each adding value. Could be slightly more concise, but structure aids readability.

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?

Given no output schema and two simple parameters, the description covers purpose, restrictions, and prerequisites. It lacks explicit mention of return value (member details), but the purpose implies retrieval. Overall, it provides sufficient context for an agent.

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 description coverage is 0%, but the description does not elaborate on individual parameters beyond mentioning 'WhatsApp ID'. The communityId parameter is not described. However, given the simplicity (two required string parameters), the description provides minimal but acceptable meaning.

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 title and description clearly state the tool retrieves a WhatsApp community member by WhatsApp ID. It distinguishes from siblings like get_whatsapp_business_member and delete_whatsapp_community_member by being a get operation. The description also clarifies that 'business' and 'community' are interchangeable, eliminating confusion.

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?

The description provides explicit when-to-use guidance: check business permissions first, note that FREE businesses cannot use it, call check_business_tool_access before collecting inputs, show grace-period warnings, and never proceed when access is blocked. It clearly defines prerequisites and constraints.

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