get_billing_portal_linkA link to the payment provider's customer portal for this account's subscription, where invoices, the payment method and cancellation live.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint, idempotentHint, and destructiveHint already present, the description adds useful context: the result is an external portal link, it is account-scoped, and it exposes billing capabilities. It omits secondary details like link expiration or auth prerequisites, but those are not critical for a simple read-only link generator.
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 concise sentence with no waste. The core object (customer portal link), the scope (this account's subscription), and the purpose (invoices, payment method, cancellation) are all stated economically.
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 zero-parameter, read-only, no-output-schema tool, this description is complete: it states what is returned (a link) and what that link provides. Sibling tools and annotations cover the remaining routing and safety context.
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?
There are zero parameters and the schema fully reflects that, so no parameter documentation is needed. The baseline for a parameterless tool applies, and the description appropriately avoids inventing parameter detail.
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 identifies the delivered resource as a link to the payment provider's customer portal, scoped to the current account's subscription. It differentiates from siblings like cancel_subscription, where cancellation lives inside the portal rather than being performed by this tool, and from get_upgrade_link by the billing/financial focus.
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 gives clear context: this tool is for surfacing billing management (invoices, payment method, cancellation) rather than performing those actions. It does not explicitly name alternatives or exclusions, but the intended use is evident from 'where invoices, the payment method and cancellation live'.
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.
Tool purposes are generally distinct and well-described, but a few clusters overlap in function: answer_screening_question vs save_answer both write to the answer book, get_my_profile vs get_account both report plan status, and the CV preview/sent-CV/base-CV tools could be confused. The detailed descriptions mitigate most misselection, so this is only a minor issue.
The set almost uniformly uses snake_case verb_noun names like list_, get_, update_, create_, delete_, and start_/stop_. Minor deviations such as login, describe_what_i_want, and the get_my_* vs list_* alternation prevent a perfect score, but the overall pattern is predictable and readable.
49 tools is far above the 25+ threshold and will burden agent tool selection even though many are legitimate single-purpose operations. Several groups could be consolidated—billing links, API-key management, and the CV PDF family—without hurting clarity.
The surface covers the full lifecycle: account creation/auth, profile and CV, targeting, matching, apply runs, screening answers, tracking, billing, export, and deletion. Minor gaps remain, such as no application-level detail/withdrawal endpoint and no direct way to save a parsed CV without re-uploading, but agents can work around them.