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 mentions pagination and filtering, but lacks critical details: whether this is a read-only operation, any rate limits, authentication requirements, error conditions, or what the output contains (though an output schema exists). For a list tool with zero annotation coverage, this is insufficient.

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 with zero waste. It front-loads the core purpose and includes key features (pagination, filtering) without redundancy or fluff.

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 moderate complexity (list operation with pagination/filtering), no annotations, and an output schema (which handles return values), the description is minimally adequate. However, it lacks context on authentication, error handling, or usage compared to siblings, leaving gaps for an AI agent to infer correct invocation.

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 schema provides no parameter descriptions. The description compensates slightly by mentioning 'pagination' (hinting at 'page' and 'limit') and 'filter by customer_id', but doesn't explain parameter purposes, defaults, or constraints (e.g., 'page' starts at 1, 'limit' max value). It adds some meaning but doesn't fully bridge the coverage gap.

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 verb ('List') and resource ('SpherePay bank accounts'), and mentions pagination and optional filtering. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_bank_account' (which likely retrieves a single account) or 'list_wallets' (which lists a different resource type).

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., authentication), compare it to 'get_bank_account' for single-account retrieval, or specify scenarios where filtering by customer_id is appropriate versus using other list tools.

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