Delete custom metadata from a payment method by supplying its token and the keys to remove, without affecting the payment method itself.
Deletes custom metadata from a payment method. This tool ONLY removes metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| keys | Yes | ||
| payment_method_token | Yes | The token of the payment method |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and idempotentHint=true. The description confirms deletion but adds no additional behavioral context such as side effects, authorization requirements, or rate limits. Minimal added value beyond annotations.
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?
Two concise sentences, front-loaded with the core action, no wasted words.
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 simple deletion tool, the description covers the basic operation but lacks parameter details for 'keys' and omits any mention of return values or error conditions. Adequate but with gaps.
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 50% (only payment_method_token has a documented description). The description does not explain the 'keys' parameter at all, leaving the agent to guess that it represents metadata keys to delete. No additional meaning is added beyond the schema.
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 'Deletes custom metadata from a payment method' with a specific verb and resource, and adds 'This tool ONLY removes metadata' to distinguish it from other payment method tools that may update or retain.
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 implies usage for deleting metadata but provides no explicit guidance on when to use this tool versus siblings like spreedly_payment_method_update or spreedly_payment_method_retain. No exclusions or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.