Invite Paywall Affiliates

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the mutation profile is covered. The description adds one genuinely useful piece beyond the annotations: the confirm=true safety gate and the fact that community state is changed. It does not describe what specifically is altered or the non-idempotent invite semantics.

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, so it is not bloated, but the first sentence earns nothing since it merely repeats the title. Front-loading is fine; the content is thin rather than padded.

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 5-parameter, nested-payload, no-output-schema destructive tool, the description covers the confirm gate but omits the three mutually exclusive body input modes (payload vs payload_file vs flags) and the credential-selecting account param. The schema carries these, so it is minimally complete but not rich.

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 every parameter (including the nested payload, payload_file mutual-exclusion rules, and existing_member_ids max of 20) is already documented. The description only echoes the confirm parameter, adding no meaning beyond the schema, so the baseline 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 first sentence is a verbatim restatement of the tool title/name with zero elaboration, which is the definition of a tautology. The action is inferable from the name, but the description itself contributes nothing to distinguish it from siblings like create_invitation or update_paywall_affiliate.

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 states a precondition ('requires confirm=true for the user-requested action'), which is a usage-relevant gate, so usage is implied rather than absent. However it never says when to pick this tool over related invite/affiliate tools, and no alternatives or exclusions are named.

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