Update Paywall Affiliate

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the operation 'changes community state' and is confirmation-gated, which is modest added context, but it omits what specifically is destroyed/changed and whether the change is reversible.

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?

It is very short and front-loaded, but the opening sentence is pure tautology that earns no place, and the substantive content ('changes community state', confirm requirement) is compressed to the point of being underspecified rather than concise.

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 6-parameter destructive mutation with a nested payload object and no output schema, the description leaves major gaps: which affiliate fields can be changed, what the status values mean, and what happens on success. The confirmation hint and vague 'community state' note are not enough to invoke this tool confidently.

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 83%, so the schema already documents most parameters including confirm, payload and payload_file. The description adds no format or meaning beyond the schema, which is the expected baseline when structured fields carry the load.

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 first sentence simply restates the tool name and title verbatim, adding no distinguishing information. The second sentence mentions 'changes community state' but never says what is actually updated on the affiliate (e.g. status), so an agent cannot tell this apart from the many other update_* siblings.

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?

It does communicate one gating condition: the action requires confirm=true and is intended for a user-requested action. However, there is no indication of when to use this tool versus alternatives such as invite_paywall_affiliates or the payout tools, and no prerequisites or exclusion conditions.

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