Enable manual payment method

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

Annotations already convey readOnlyHint=false and destructiveHint=false, so the description's burden is light. It adds post-condition context (store can accept orders without a provider), which is useful, but it doesn't disclose preconditions, reversibility, or side effects beyond the enabling action.

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?

A single 18-word sentence that front-loads the verb and object, then explains the purpose. Every word earns its place; there is no filler or repetition of the tool name.

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 low-complexity tool with fully documented parameters and annotations covering the safety profile, the description answers what the tool does, to which store, and with what effect. The only gap is explicit routing guidance against the payment-provider-connect sibling, which is minor for such a simple action.

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 100%, so the schema fully documents store_id and title, including title's display-name semantics at checkout. The description adds no additional parameter-level meaning beyond the schema, which matches the baseline 3 for high coverage.

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 states a specific verb ('Enable'), a clear resource ('a manual payment method'), and the business effect ('so the store can accept orders without an online payment provider'). This distinguishes it from siblings like ecommerce_createAPaymentProviderConnectLinkV1, which handles online providers instead.

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 phrase 'without an online payment provider' implies the use case — enabling manual payment for stores that lack an online provider — but the description never explicitly names alternatives or states when not to use this tool. Usage context is present but only implied.

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