Pull-verify a Stripe session/subscription and idempotently activate its exact subscription period. A newly created account receives its key once.
| Name | Required | Description | Default |
|---|---|---|---|
| stripe_session_or_sub_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It usefully states the operation is idempotent and that a newly created account receives its key once, which are important side-effect semantics. It does not detail permissions, failure modes, or reversibility, but the provided behavior is non-trivial and valuable.
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, front-loaded with the primary action, and contains no redundant wording. Every phrase adds useful context, including idempotency and the one-time key behavior.
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 the simple one-parameter signature and presence of an output schema, the description covers the key operational context: verifying a Stripe identifier, activating the exact period, idempotency, and the key-delivery condition. It lacks explicit when-to-use guidance but is otherwise complete for a tool of this complexity.
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 clarifies that the single parameter is a Stripe session or subscription identifier used for pull-verify and activation. However, it does not add format, validation, or ownership constraints beyond what the parameter title already suggests.
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 clearly states the action: 'Pull-verify a Stripe session/subscription and idempotently activate its exact subscription period.' It names a specific resource (Stripe session/subscription) and a precise outcome, distinguishing it from sibling read-only tools like subscription_status or creation tools like create_checkout_link.
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 implies usage after a Stripe session or subscription exists (pull-verify then activate), and the phrase 'newly created account' hints at a post-account-creation workflow. However, it does not explicitly name alternatives, prerequisites, or conditions where this tool should be avoided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes: plan retrieval, checkout, portal, status, usage, MRR. The main overlap is between create_account and record_subscription, as record_subscription can create an account for a new bearer, which may confuse agents about when to call which.
The majority follow a verb_noun pattern (create_account, create_checkout_link, get_plan, list_plans, record_subscription). A few deviate: customer_portal_link (noun phrase), mrr_summary (acronym), and describe_agent (verb but not a subscription action), which slightly reduces consistency.
Ten tools is well within the ideal range for a subscription management server. Each tool covers a distinct aspect of the domain—account, plans, checkout, portals, subscriptions, usage, MRR—so none feel redundant or missing.
The tool surface covers account creation, plan browsing, checkout session creation, subscription activation, status checks, usage summaries, and MRR. A notable gap is the lack of direct update/cancel subscription tools, though this is partially mitigated by the customer portal link, which delegates those actions to Stripe's hosted UI.