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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the read-only nature is clear. The description adds valuable behavioral context about access restrictions (free businesses blocked) and required pre-checks, which goes beyond what annotations provide. No contradiction.

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 moderately concise, with the first sentence stating the purpose and subsequent sentences providing critical usage instructions. It is front-loaded but could be slightly more streamlined by separating core purpose from auxiliary checks.

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?

The description covers access restrictions and prerequisites well, but it lacks information about the return value (no output schema) and does not explain the parameters beyond the mention of WhatsApp ID. For a simple read operation, this is adequate but leaves gaps for an AI 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 has 0% description coverage for parameters. The description only mentions 'by WhatsApp ID' but does not explain the communityId parameter or their semantics. With no schema descriptions, the description should compensate, but it does not fully explain what each parameter represents or how to obtain them.

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 clearly states 'Get a WhatsApp community member by WhatsApp ID' and clarifies that 'Business and community are interchangeable.' This makes the action clear, though the sibling tool get_whatsapp_community_member exists, and the description does not differentiate between them, potentially causing 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 guidance: check business permissions before offering, FREE businesses cannot use, call check_business_tool_access before collecting inputs, and show grace-period warning and verified resubscribe link. It clearly states when not to proceed, making it highly actionable.

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