SpherePay MCP Server

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a write operation ('execute'), mentions automatic idempotency handling, lists required parameters, and specifies supported networks. However, it doesn't cover error conditions, rate limits, or authentication requirements.

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 efficiently structured with two sentences: the first establishes core functionality and requirements, the second covers idempotency and network support. Every element serves a purpose with no wasted words, and critical information appears first.

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 complex money transfer tool with 8 parameters, 0% schema coverage, and no annotations, the description provides substantial context about parameters, idempotency, and networks. Since an output schema exists, the description doesn't need to explain return values. The main gap is lack of error handling or authentication 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?

With 0% schema description coverage, the description compensates well by explaining the purpose of 7 required parameters and providing context about network options. It clarifies that source_id and destination_id refer to 'bank account or wallet IDs' and lists supported networks, adding significant value 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 specific action ('execute a money transfer'), identifies the resources involved ('between funding instruments'), and distinguishes from sibling tools by focusing on execution rather than creation, retrieval, or listing operations. It provides a complete picture of what the tool does.

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 implies usage context through parameter requirements and network support details, but doesn't explicitly state when to use this tool versus alternatives like 'get_transfer' or 'list_transfers'. No explicit guidance on prerequisites or exclusions is provided.

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