Get a Stripe Billing Portal URL for the human to manage their subscription — update payment methods, view invoices, change plans, or cancel. Requires an existing Stripe subscription.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Stripe Billing Portal URL — present this to the human |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint: true and openWorldHint: true, so the description's role is reduced. The description adds value by specifying the requirement of an existing subscription and that it returns a URL for human interaction. There is no contradiction with annotations. The behavioral disclosure is adequate.
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, tightly crafted sentence that front-loads the core purpose, lists capabilities, and states the requirement. No extraneous words or redundancy. Every element 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?
For a no-parameter tool with an output schema (indicated by context), the description is fully complete. It explains what the tool does, what is required, and what the output is (a URL for human management). There are no gaps given the tool's simplicity.
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 tool has no parameters, so baseline score is 4 per guidelines. The description does not need to add parameter information.
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 verb ('Get'), the resource ('Stripe Billing Portal URL'), and the purpose ('for the human to manage their subscription'). It lists specific actions the portal enables (update payment methods, view invoices, change plans, or cancel), distinguishing it from sibling tools like billing.create_checkout or billing.status.
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 explicitly states a precondition: 'Requires an existing Stripe subscription.' This provides clear context on when the tool is applicable. However, it does not explicitly mention when not to use it or point to alternative tools, though the context is sufficient given the tool's simplicity.
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 resource+action naming (e.g., leads.create, jobs.list), but some overlap exists in analytics tools (dashboard, detailed, financials) and workflow automations (process_lead vs google_ads_pipeline). Descriptions clarify purposes, so slight confusion is possible but limited.
All tools follow a consistent `domain.action` pattern (e.g., leads.create, billing.status). No mixing of camelCase or snake_case. Even complex names like lifecycle.assess or scaling.readiness_score adhere to the convention.
95 tools is far beyond typical well-scoped servers (3-15). While the server aims to cover an entire business management platform, this volume is overwhelming for an agent, making selection and memory difficult.
The tool surface is exceptionally comprehensive, covering formation, hiring, compliance, funding, leads, quotes, jobs, invoicing, payments, marketing, analytics, integrations, webhooks, workflows, and more. Almost no obvious gaps in the lifecycle of running a trade business.