SpherePay MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is for 'submitting' a transaction, implying a write/mutation operation, but doesn't cover critical aspects like required permissions, whether it's idempotent, rate limits, error handling, or what happens upon success (e.g., confirmation of redemption). This leaves significant gaps for an agent to understand the tool's 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?

The description is appropriately sized and front-loaded: the first sentence states the core purpose, and subsequent sentences efficiently explain each parameter. There is no wasted text, and the structure is clear and direct.

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 that there is an output schema (which handles return values), no annotations, and 3 parameters with 0% schema coverage, the description is moderately complete. It covers the purpose and parameter semantics well but lacks behavioral details and usage guidelines. For a mutation tool with no annotations, it should do more to explain side effects and prerequisites.

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 adds meaningful semantics for all three parameters: it specifies that 'source_chain' accepts 'sei' or 'noble', 'source_transaction_hash' is 'the burn transaction hash from the source chain', and 'transfer_id' is 'the payout/transfer ID (format: payout_...)'. This clarifies the purpose and format of each parameter beyond the bare schema.

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 tool's purpose: 'Submit a CCTP (Cross-Chain Transfer Protocol) burn transaction for off-ramp redemption.' It specifies the action (submit), resource (CCTP burn transaction), and context (off-ramp redemption). However, it doesn't explicitly distinguish this tool from sibling tools like 'execute_transfer' or 'setup_funding', which might handle similar financial operations.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a burn transaction first), exclusions, or how it differs from sibling tools like 'execute_transfer' or 'get_transfer'. The context is implied through parameter details but lacks explicit usage instructions.

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