Change Billing Plan

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

The destructiveHint annotation indicates this is a mutating action, but the description adds no context about billing impact, reversibility, or potential side effects. It does not contradict the annotations, but it also does not meaningfully expand on them.

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 a single, front-loaded sentence with no unnecessary words. It is concise, though arguably too terse to fully support agent decision-making.

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 description lacks important context such as return behavior, relationship to listTiers or getWorkspaceBilling, and any caveats about changing a billing tier. Given the action's destructive nature, more contextual detail is 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?

The parameter names workspaceSlug and tier are somewhat self-explanatory, but the description does not clarify where to obtain the slug or what tier values are accepted. The schema only provides a generic description for requestBody and no domain-specific explanation.

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 clear verb and resource: changing the workspace billing tier. It is distinct from read-only tools like getWorkspaceBilling and listTiers, though it does not specify what tier values are valid.

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?

No guidance is provided on when to use this tool versus related billing tools, such as listing available tiers first or checking current billing state. The description gives no prerequisites or conditions for calling it.

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