Delete Base Plan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add useful conditions: only inactive base plans with no active subscribers can be deleted and the tool is disabled in read-only mode. But for a destructive operation it omits consequences like permanence, cascading effects, or permission requirements.

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 three short sentences with no filler. The primary action is stated first, followed by the most important eligibility constraint and the read-only mode restriction, making it easy for an agent to scan and act on.

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?

The full parameter schema and presence of an output schema cover invocation details, and the description provides essential preconditions. However, it lacks guidance about how this tool relates to deactivate_base_plan or what to do with an active base plan, which is a meaningful gap for an agent navigating many sibling subscription tools.

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 all three parameters already described in the input schema. The description adds little parameter-level meaning beyond reinforcing that this targets a subscription base plan, so the baseline score 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 states a specific verb and resource: 'Delete a subscription base plan.' It also adds distinguishing preconditions that separate deletion from mere deactivation, which helps differentiate it from sibling tools like deactivate_base_plan. However, it does not explicitly contrast itself with those siblings, so it stops short of full differentiation.

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 context for when deletion is permitted: only inactive base plans with no active subscribers, and it notes the tool is disabled in read-only mode. It does not, however, point to alternatives such as deactivate_base_plan for plans that are still active, so alternative routing is absent.

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