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

The description states the tool deletes a payout account, which is a destructive action. However, the annotations indicate destructiveHint=false, contradicting the description. This contradiction misleads the agent about the tool's safety profile.

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 dense with information, but structured in a single paragraph. It front-loads key points (delete, requires confirm). Every sentence adds value, though it could be slightly more organized with bullet points or clearer breaks.

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 the tool's complexity as a delete operation with prerequisites and restrictions, the description covers all critical aspects: required parameter value, business/context clarification, permission checks, free business restriction, prerequisite tools, and user-facing warnings. No output schema exists, but the return behavior is adequately implied.

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?

The input schema has 0% description coverage, so the description must compensate. It adds that the confirm parameter must be set to 'DELETE', which is critical. However, it does not elaborate on communityId or payoutAccountType beyond their names, leaving some ambiguity.

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 it deletes a payout account configuration for a managed community. The verb 'Delete' is specific, and the resource is identified. It distinguishes from sibling tools like create_business_payout_account and get_business_payout_account.

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 usage guidelines: requires confirm='DELETE', notes that business/community are interchangeable, requires permission checks, warns that FREE businesses cannot use, instructs to call check_business_tool_access before collecting inputs, and specifies showing grace-period warning and verified resubscribe link. This fully guides when and how to use the tool.

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