Delete Payment Method

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

No annotations are provided, so the description must disclose behavioral traits like irreversibility, effects on subscriptions, or default payment method handling. It only restates the tool's name ('Delete a payment method') with no additional context, failing to convey important implications of the deletion.

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 concise sentence that is front-loaded and contains no redundant words. It is appropriately sized for the simplicity of the tool, though it lacks substance in other dimensions.

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 simplicity of the tool (one required parameter, no output schema), the description is minimal but missing critical context about deletion consequences, such as irreversibility or impact on subscriptions. The lack of behavioral disclosure makes it incomplete for an agent to fully understand the operation's impact.

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 schema provides 100% coverage for the single parameter 'payment_method_id' with a description, so the description doesn't need to add parameter details. Per the baseline, a score of 3 is appropriate since the schema already documents the parameter adequately.

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 'Delete a payment method' clearly states the action (delete) and the resource (payment method), distinguishing it from sibling tools like billing_get_payment_methods and billing_set_default_payment_method. It is specific and unambiguous, though it doesn't add any extra detail beyond the title.

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 usage is implied by the tool's name and description: when you want to remove a payment method. There is no explicit guidance on when to use it versus alternatives, but the sibling context makes the purpose clear. No when-not or alternative recommendations are provided.

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