delete_subscription

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

With no annotations present, the description carries the burden of behavioral disclosure. It transparently states that the tool deletes a Subscription and that setting also_delete_csv=True additionally removes the installed CSV, which is a meaningful side effect. However, it does not mention irreversibility, required permissions, or downstream effects on the operator.

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 two sentences with no filler. The core action is front-loaded, and the optional flag is explained immediately after with a clear conditional. Every word earns its place.

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 tool is a simple 4-parameter delete with an output schema, so the return format does not need to be described. The description covers the action and the key option. Minor gaps remain: the acronym CSV is not expanded, and there is no mention of what happens to the operator when the subscription is deleted, but nothing blocks correct invocation.

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 0%, so the description must compensate. It explicitly explains the meaning and effect of also_delete_csv, which is the least obvious parameter. The remaining parameters (name, cluster, namespace) are left to their self-explanatory titles, so the description does not fully compensate for the missing schema descriptions.

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 an OLM Subscription." It clearly distinguishes this tool from siblings such as create_subscription and list_subscriptions, and adds the optional CSV-removal behavior, which further clarifies the tool's scope.

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 intended use is implied by the name and action, but the description gives no explicit guidance about when to choose this over alternatives or any conditions or prerequisites. There is no mention of when not to use it or how it relates to other subscription-management tools.

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