rendben_get_subscription_statusRead the payer-safe status of an opaque subscription authorization after its transaction has been submitted.
| Name | Required | Description | Default |
|---|---|---|---|
| subscriptionId | Yes | Opaque sub_ subscription authorization ID returned by Rendben. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is clear. Description adds that it returns 'payer-safe' status, implying data is masked/untrustworthy—useful beyond annotations. No mention of rate limits or failure behavior.
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?
Single sentence, front-loaded with 'Read' purpose. No fluff. Could slightly improve by adding sibling differentiation in same sentence.
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 simple 1-param read tool with good annotations and 100% schema coverage, description provides necessary info. Lacks mention of no output schema, but that's fine per rules. Minor gap: doesn't clarify what 'payer-safe' means for agent.
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?
Only parameter is subscriptionId with 100% schema coverage, so schema does most work. Description adds that it's 'opaque sub_ subscription authorization ID returned by Rendben', reinforcing schema context. Baseline 3 is correct.
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?
Clearly states it reads a subscription authorization status after transaction submission. Verb is 'Read' and resource is specified ('opaque subscription authorization'). Differentiates from siblings in that it's post-transaction, but doesn't explicitly contrast with get_payment_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?
Implies usage is after a transaction is submitted, but no explicit when-to-use vs. when-not-to-use, nor guidance on alternatives like get_payment_status. Context signals show siblings are payment-oriented, but description doesn't leverage that.
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.
Each tool targets a distinct action: creating payment intents, querying payment/subscription status, inspecting checkouts, and preparing payments. No two tools appear to overlap in purpose.
All tools consistently follow the `rendben_verb_noun` pattern in snake_case (e.g., create_payment_intent, inspect_checkout). There are no deviations or mixed conventions.
With 6 tools covering payment intent creation, status checks, checkout inspection, and payment preparation, the count is well-scoped for a focused payment server without being excessive or sparse.
The tool set covers core actions (create, check, prepare) but notably lacks tooling for signing/submitting transactions or managing refunds/cancellations. The preparation tools explicitly leave signing to the user, creating a workflow gap for an autonomous agent.