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

Description states 'Delete' implying destructive action, but annotations have destructiveHint=false, a direct contradiction. Also claims confirm parameter is required, but schema lists it as not required. Lacks disclosure of other behavioral traits.

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?

Multiple sentences with essential warnings, but could be more concise. Information is front-loaded and relevant.

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, so description should compensate but does not discuss return values. Important contradictions reduce completeness for a deletion tool.

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 coverage is 0%, but description adds some meaning for confirm (must be 'DELETE'), but contradicts schema as not required. No info on whatsappId or communityId beyond schema names.

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?

Description states 'Delete a WhatsApp community member' which is clear verb and resource. However, it mentions that 'Business and community refer to the same thing and are interchangeable', but sibling list includes both delete_whatsapp_business_member and delete_whatsapp_community_member, causing potential confusion. Also contradicts schema by requiring confirm parameter.

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 guidelines: check business permissions, FREE businesses cannot use, call check_business_tool_access, show warnings before proceeding. Clear context for when to use.

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