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

Annotations already indicate destructiveHint: true. Description adds context: requires confirm set to UPDATE_SUBSCRIPTION, business/community equivalence, access prerequisites. However, it doesn't detail the exact outcomes of setting cancellation (e.g., immediate effect, scheduling) or failure scenarios, leaving some behavioral gaps.

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 moderately concise; each sentence adds value. It is front-loaded with purpose and then prerequisites/instructions. Minor redundancy (e.g., 'Business and community ... interchangeable') but overall efficient.

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 tool with 5 parameters, the description covers important business rules and prerequisites but omits parameter details and return values. Given no output schema, more completeness is needed for safe usage.

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?

With 0% schema coverage, the description must explain parameters. It only hints at 'confirm' needing a specific value, but communityId, orderObjectId, cancelSubscription, and cancellationReasons are left unexplained. This significantly hinders correct invocation.

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 in a managed community, using specific verbs and resources. It addresses the interchangeability of 'business' and 'community' but doesn't explicitly differentiate from siblings like 'set_custom_domain_subscription_cancellation', limiting distinction.

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 prerequisites are given: check business permissions, FREE businesses cannot use, call check_business_tool_access, show grace-period warning and resubscribe link, never proceed when blocked. This provides clear when-to-use guidance, though alternative tools are not named.

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