Export Paywall Affiliate Payouts

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds the useful, non-obvious fact that the call requires confirm=true, but it never explains what the destructive aspect actually does (what state changes, what is exported, where the export lands), leaving the most consequential behavior unexplained.

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?

Two short sentences with the action stated first and the confirmation requirement second; nothing is padded. It is efficient, though the first sentence is pure duplication of the title rather than new information.

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, non-idempotent, open-world tool with no output schema and a nested payload object, the description is too thin: it never explains what the export produces, where results go, or what 'changes community state' means for payouts. An agent would have to guess at the observable outcome of the call.

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 100%, so all five parameters are documented in the schema, including the account/credential distinction, the max-20 community_member_ids scoping, and the payload vs payload_file mutual exclusion. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 states a verb ('Export') and a resource ('Paywall Affiliate Payouts'), but the first sentence is a verbatim restatement of the tool title and adds no scope detail. It does nothing to distinguish this export from siblings such as start_paywall_affiliate_payouts, mark_paywall_affiliate_payouts_paid, or list_paywall_affiliates, so the agent cannot tell which payout-related tool to pick from the description alone.

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 only guidance is the confirm=true gate, which is an execution precondition rather than a statement of when this tool is appropriate versus its payout siblings. There is no mention of when to use export vs list or vs the start/mark-paid flows, and no exclusions.

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