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

Annotations indicate destructiveHint: true. The description adds value by specifying the confirm requirement as a safety mechanism and outlining access checks. It does not contradict annotations and provides context about the destructive nature of updating cancellation state. It could be improved by detailing what happens when cancelSubscription is toggled.

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 relatively concise at five sentences, with the purpose front-loaded. It includes necessary safety and prerequisite information. However, the clarification that 'Business and community refer to the same thing' adds slight confusion and could be more succinctly integrated.

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 (5 parameters, destructive, no output schema), the description covers the main purpose, prerequisites, and the confirm requirement. However, it fails to describe the effect of the cancelSubscription boolean, the role of orderObjectId, or the cancellationReasons array. It also does not hint at return values or error conditions, leaving gaps for a complete understanding.

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 0%, so the description must compensate. It only explains the 'confirm' parameter (requires 'UPDATE_SUBSCRIPTION'), leaving communityId, orderObjectId, cancelSubscription, and cancellationReasons unexplained. Users are left to infer their meanings from the tool name and context, which is insufficient.

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 the tool updates subscription cancellation state for a custom-domain order. It uses specific verbs ('update', 'requires') and identifies the resource. However, it does not differentiate from the very similar sibling tool 'set_community_custom_domain_subscription_cancellation', and it mentions that 'Business and community refer to the same thing', which could cause confusion.

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 description provides explicit usage guidelines: it requires confirm set to 'UPDATE_SUBSCRIPTION', mandates checking permissions and calling check_business_tool_access before proceeding, warns that FREE businesses cannot use it, and instructs to show grace-period warnings and resubscribe links. This is excellent guidance, though it does not explicitly mention alternatives.

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