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

Annotations indicate destructiveHint=true. The description adds that a confirmation parameter is required, that FREE businesses are blocked, and that permission checks are necessary. It also prescribes UI steps before action. This provides context beyond annotations without contradiction.

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 a single paragraph with multiple sentences, but each sentence adds value. It is concise without being terse. There is some redundancy (business/community interchangeable). Could be slightly more structured, 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?

The description covers permissions, prerequisites, and constraints, but does not explain the 'metadata' or 'directCharge' parameters, nor the output or possible side effects. No output schema exists to fill gaps. Given 5 parameters, nested objects, and no output schema, the description is incomplete.

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 0%, so the description must compensate. It explains that the 'confirm' parameter must be set to 'UPDATE_PAYMENT_METHOD', but does not explain 'metadata', 'directCharge', or the meaning of 'communityId' and 'orderObjectId' beyond being required. Only one parameter gets meaningful context.

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 'Update the payment method for a custom-domain order in a managed community.' It mentions that business and community are interchangeable, but there is a sibling 'update_community_custom_domain_payment_method', so differentiation is not strong. However, the business context is explicit.

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 guidance: requires 'confirm' set to 'UPDATE_PAYMENT_METHOD', advises checking business permissions, states FREE businesses cannot use it, instructs to call check_business_tool_access before collecting inputs, and mandates showing grace-period warnings and verified resubscribe links before proceeding. It also warns never to proceed when access is blocked.

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