Buy Orchyn Credits

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, etc.), the description discloses key behavioral details: the call itself costs nothing, it returns a Stripe checkout URL that the user must open in a browser, and credits are added automatically after payment. This explains the external payment flow and separates 'calling the tool' from 'paying,' which is valuable context for an agent.

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 compact and front-loaded: 'Buy an MCP credit pack via Stripe Checkout' immediately states the action. Three short sentences cover the return value, payment flow, automatic credit addition, cost, and usage condition, with no filler or redundancy.

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 tool with an output schema, the description is complete: it explains the return URL, the browser step, the automatic credit addition, the credit cost, and when to call the tool. An agent has everything needed to invoke it correctly without further ambiguity.

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, so the schema naturally has 100% coverage and no parameter-level documentation is needed. The description adds context about what the tool returns and how the operation works, which is more than enough for a parameterless tool. No parameter gaps exist to compensate for.

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 states a specific verb and resource: 'Buy an MCP credit pack via Stripe Checkout.' It also explains the operational outcome (returns a secure checkout URL), which clearly distinguishes it from siblings like check_orchyn_credits that check balance. The title and description align, and the purpose is unmistakable.

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 an explicit when-to-use condition: 'Use when the balance is short and the user has agreed to top up.' This provides clear situational context and a user-consent gate. It does not name alternatives or state when not to use it, but the condition itself is sufficient for an agent to route correctly.

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