stripe-upgradeSubscription

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

Annotations provide idempotentHint and openWorldHint, but the description adds zero behavioral context beyond that. It does not mention what changes occur (e.g., billing, plan tier), side effects, or security considerations. The description carries no additional value.

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 (one line), but it is under-specified to the point of being unhelpful. Conciseness should not come at the expense of clarity; here it fails to convey necessary information.

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?

No output schema, no behavioral description, and incomplete parameter semantics. For a mutation tool, the description should explain what the upgrade does (e.g., changes tier, quantity, billing cycle) and any limitations. It is completely inadequate for safe and correct agentic use.

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%, and the description provides no explanation of the parameters (tier, serverQuantity, isAnnual). The agent must infer meaning solely from names and schema constraints. The description adds no semantic value.

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 is 'POST /stripe.upgradeSubscription', which is a tautology that merely repeats the tool name and HTTP method. It fails to specify what upgrading a subscription entails or how it differs from other Stripe tools like stripe-createCheckoutSession or stripe-getCurrentPlan.

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 on when to use this tool versus alternatives. The description provides no context about prerequisites, scenarios, or when not to use it. The only implicit hint is the word 'upgrade', but it's insufficient for an agent to make a decision.

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