paymentMethods.delete

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

No annotations provided, so description carries full burden. States 'Delete' but fails to disclose if this is permanent, if it fails when the method is in use by subscriptions, or required permissions. Minimal safety context for a destructive operation.

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?

Single sentence, front-loaded with active verb. No wasted words. However, extreme brevity leaves critical gaps given lack of annotations and schema descriptions.

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?

Inadequate for a destructive mutation tool. Lacks coverage of error cases (e.g., payment method in use), reversibility, or side effects. With no output schema and 0% param coverage, description should provide more operational context.

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 0% (id parameter undocumented). Description mentions 'payment method' but adds no syntax, format, or semantic details about the 'id' parameter itself. Fails to compensate for schema description gap.

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?

Clear verb ('Delete') and resource ('Ryft payment method'), distinguishing it from siblings like customers.delete or payouts.delete. However, it does not differentiate from other payment method operations (update/get).

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?

Provides no guidance on when to use this versus detaching a payment method from a customer, or prerequisites like ensuring no active subscriptions use this method. No alternative actions mentioned.

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