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 describes the creation action and return values (customer with TOS/KYC links), which is helpful. However, it doesn't mention important behavioral aspects like authentication requirements, rate limits, error conditions, or whether this is an idempotent operation, leaving significant gaps.

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 perfectly concise and front-loaded. The first sentence states the core purpose, followed by specific details about customer types and parameters, then concludes with return values. Every sentence earns its place with no wasted words.

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 complexity (10 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description does well by explaining parameter semantics and return values. However, for a customer creation tool in a financial context, it should ideally mention authentication requirements or permissions needed, which is a minor completeness gap.

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 excellently by explaining the semantics of parameters. It clarifies that 'customer_type' supports 'individual' and 'business' values, specifies which parameters are required for each type (address for individual, business_information and addresses for business), and distinguishes optional fields (first/last name, DOB). This adds substantial 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 tool's purpose with specific verbs ('Create', 'generate') and resources ('SpherePay customer', 'verification links'). It distinguishes this from sibling tools like 'get_customer' (which retrieves) and 'verify_customer' (which verifies), establishing it as a creation tool.

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 clear context about when to use this tool by specifying the two customer types ('individual' and 'business') and their required fields. However, it doesn't explicitly state when NOT to use it or mention alternatives like 'onboard_business_rep' for business representatives, which is a minor gap.

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