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

The description states 'Delete a WhatsApp community member,' indicating destructive behavior, but annotations have destructiveHint=false, creating a contradiction. The description does not resolve this and omits other behavioral context such as idempotency or error handling. Despite adding permission checks and prerequisites, the contradiction undermines transparency.

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 concise but contains a few clarifying sentences that are slightly redundant (e.g., 'Business and community refer to the same thing'). Overall, it is well-structured and front-loaded with the main action, with each sentence contributing to usage guidance.

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 3 parameters with 0% coverage, the description covers usage workflow and prerequisites but lacks details on return values (e.g., success indication) or parameter descriptions for all fields. It is partially complete for an agent to invoke correctly.

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%. The description clarifies that 'confirm' must be set to 'DELETE', adding meaning beyond the schema. However, it does not explain 'whatsappId' or 'communityId' beyond their names, so only partial value is added.

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 'Delete a WhatsApp community member' with a specific verb and resource. The name and description distinguish it from sibling tools like delete_whatsapp_business_member and remove_community_member, though not explicitly.

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?

Provides explicit guidance: requires 'confirm' set to 'DELETE', check business permissions, FREE businesses cannot use, call check_business_tool_access first, show grace-period warning and resubscribe link, and never proceed when blocked. This includes when-not-to-use and prerequisites.

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