deletePaymentMethod

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

With no annotations provided, the description fully carries the burden of disclosing behavioral traits. It labels the tool as 'DESTRUCTIVE' and details specific consequences: saved details removed and auto-charges will fail. It also explains the host's confirmation enforcement via the approval gate, covering both safety and workflow behavior.

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 exceptionally concise, consisting of two sentences that each add critical value. The first sentence states the primary action and its destructive nature, while the second provides usage guidelines and behavioral context. No unnecessary words or repetition.

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 simplicity (a delete operation), the description is complete. It explains the outcome, consequences, and the host's approval workflow. There is no output schema, but the description sufficiently covers what the agent needs to know to invoke the tool correctly.

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?

The input schema has 100% description coverage, providing full details for the two required parameters (customerId, paymentMethodId). The description does not add new parameter information beyond what the schema already provides, so it meets the baseline for high schema coverage without exceeding it.

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's action: 'Permanently delete a payment method from a customer.' It specifies the resource (payment method) and the consequence (removal of card/bank details, causing recurring charges to fail). This distinguishes it from sibling tools like attachPaymentMethod or listPaymentMethods.

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 when-to-use guidance: 'Only call when the user explicitly says delete for THIS payment method.' It also instructs the agent not to ask for re-confirmation because the host already enforces confirmation via the approval gate. This clearly communicates usage constraints and behavior.

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