SpherePay MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a wallet for off-ramping, implying a write operation, but lacks details on permissions, side effects, rate limits, or response behavior. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence that front-loads the purpose and lists parameters without waste. Every word contributes essential information, making it appropriately sized and well-structured.

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 tool's complexity (a write operation with 4 parameters), no annotations, and an output schema (which reduces need to describe returns), the description is partially complete. It covers the basic purpose and parameters but lacks behavioral details and usage context, making it minimally adequate but with clear gaps.

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 lists all four parameters and adds semantic context: 'customer_id' for identification, 'currency' with examples ('usdc', 'usdt', 'eurc'), 'network' as blockchain, and 'wallet_address' for the target. This clarifies purpose beyond the bare schema, though it doesn't specify formats or constraints.

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 ('Create') and resource ('offloader wallet') with its function ('automatic stablecoin-to-fiat off-ramp'). It distinguishes from siblings like 'setup_funding' or 'setup_virtual_account' by specifying the wallet's purpose, though it doesn't explicitly contrast them. The purpose is specific but lacks explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'setup_funding' or 'setup_virtual_account', nor does it mention prerequisites beyond the required parameters. The description implies usage for off-ramping but offers no context on timing, exclusions, or comparisons with sibling tools.

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