Rebillia MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' clearly indicates a destructive operation, the description fails to mention important behavioral aspects: whether deletion is permanent/reversible, what permissions are required, what happens to associated data, or any rate limits. The HTTP method reference adds minimal value beyond the obvious destructive nature.

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 with just two sentences that directly state the action and provide the HTTP endpoint. There's zero wasted language, and the most critical information ('Delete a rate plan') appears first, making it well-structured for quick comprehension.

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 explain what 'delete' entails operationally, what the response looks like, error conditions, or dependencies. Given the high-stakes nature of deletion tools, more contextual information would be expected.

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%, so the schema already fully documents the single required parameter. The description adds no additional semantic context about the ratePlanId parameter beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 ('a rate plan'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'delete_product_rate_plan_charge' or 'delete_product', but the specificity of 'rate plan' provides reasonable distinction.

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 like 'delete_product' or 'delete_product_rate_plan_charge'. It also doesn't mention prerequisites, dependencies, or consequences of deletion, leaving the agent with insufficient context for appropriate tool selection.

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