delete_base_plan

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

The description does not disclose behavioral traits beyond the basic fact that it is a delete operation. It mentions limitations on eligibility and read-only mode, but no annotations are provided, so the description carries the full burden. It fails to mention what happens to associated data, whether the deletion is reversible, or any error responses.

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 a single sentence plus a short note about the eligibility and read-only mode. Every sentence adds value, and there is no redundancy or filler.

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 that this is a destructive operation with no annotations and no output schema, the description should provide more context about what happens after deletion, any side effects, or permission requirements. It is too minimal for the complexity of a delete operation.

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 input schema provides descriptions for all three parameters (product_id, base_plan_id, package_name), covering 100% of the schema. The description does not add additional meaning beyond what the schema states, so a baseline of 3 is appropriate.

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 tool's action ('Delete a subscription base plan') and identifies the specific resource. It distinguishes itself from sibling tools like 'delete_subscription' and 'delete_subscription_offer' by focusing on 'base plan'.

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 clear conditions for when the tool can be used ('Only inactive base plans with no active subscribers can be deleted') and mentions that it is disabled in read-only mode. However, it does not explicitly contrast with alternatives or state when another tool should be used, leaving room for a dedicated usage section.

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