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

Goes well beyond the annotations by disclosing the confirmation requirement, permission gating, tier restriction, and warning-display obligations. It does not say whether the deletion is reversible or what happens to pending payouts, and it does not address the tension that annotations declare destructiveHint=false for a delete operation.

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?

Front-loaded with the action, then ordered prerequisites (permissions, tier check, warnings). Every sentence carries an operational constraint, though the sequence of gating instructions is dense enough to read as a checklist rather than a description.

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?

For a destructive write with three parameters and full schema coverage, the description supplies the permission and confirmation choreography an agent needs to avoid a bad call. The main remaining gap is consequence information — reversibility and effect on in-flight payments — which no other structured field covers.

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 100%, so the baseline is 3. The description only reinforces the confirm literal ("Requires confirm set to DELETE"), which the schema already conveys; it adds nothing about communityId or payoutAccountType beyond the schema text.

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?

"Delete payout account configuration for a managed community" gives a specific verb, resource and scope, and the note that "Business and community refer to the same thing and are interchangeable" disambiguates it from the parallel delete_community_payout_account naming. It stops short of explicitly stating which of the two similarly named tools an agent should pick, so a 4 rather than a 5.

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?

Explicit preconditions and exclusions: call check_business_tool_access before collecting inputs, FREE businesses cannot use this tool regardless of feature rows, show grace-period warnings and resubscribe link, and never proceed when access is blocked. It names the prerequisite sibling tool and the blocking condition, leaving little to inference.

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