Rebillia MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't specify whether this is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting active subscriptions). The HTTP method (DELETE) is mentioned but doesn't add meaningful behavioral context for an AI agent.

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 extremely concise—two sentences with zero wasted words. The first sentence states the core purpose, and the second provides technical context (HTTP endpoint). Every element earns its place, and the information is front-loaded appropriately for quick understanding.

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 destructive operation with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context: what happens after deletion, error conditions, authentication requirements, or what the tool returns. Given the complexity of payment method management and multiple sibling tools, more behavioral and usage context is needed.

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 description coverage is 100%, with both parameters clearly documented as required IDs. The description adds no additional parameter semantics beyond what the schema provides—it doesn't explain format expectations, sourcing, or relationships between customerId and paymentMethodId. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 action ('Delete') and resource ('payment method'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_customer' or 'delete_customer_address' by specifying the exact resource type. However, it doesn't explicitly differentiate from 'update_customer_payment_method' in terms of operation type beyond the verb.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the payment method must be inactive), consequences (e.g., impact on subscriptions), or when to choose deletion over updating. With multiple sibling tools for customer resources, this lack of contextual guidance is a significant gap.

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