Cancel an AgentaOS subscription at period end by default, or immediately with now=true.
Cancel a subscription (at period end by default)
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The subscription id | |
| now | No | Cancel immediately instead of at the end of the current period |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses one key trait—cancellation happens at period end by default—but omits irreversibility, required permissions, billing effects, and what happens to access after cancellation.
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?
A single front-loaded sentence with zero waste. The most important information—the action and its default timing—appears immediately.
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 no annotations and no output schema, the description should do more for a destructive cancel operation. It covers purpose and default timing but leaves critical context gaps around consequences, reversibility, and permissions.
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 documents both parameters. The description adds value by explicitly stating that period-end cancellation is the default, clarifying the effect of leaving the 'now' parameter unset.
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 ('Cancel a subscription') and adds the default timing. This clearly distinguishes it from sibling tools like agenta_subscriptions_list and agenta_subscriptions_change_plan without needing to name them.
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?
There is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The parenthetical states a default behavior, but does not address when immediate cancellation is appropriate or what conditions warrant cancellation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.