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 retrieves account details and returns status, which implies a read-only operation, but doesn't cover aspects like authentication requirements, error handling, or rate limits, leaving significant gaps in transparency.

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 concise and front-loaded, using two clear sentences that state the purpose and return value without unnecessary details. It efficiently communicates core information, though it could be slightly more structured by including usage context.

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 simplicity (one parameter) and the presence of an output schema, the description covers basic purpose and return scope adequately. However, with no annotations and incomplete behavioral details, it lacks depth for a fully informed agent, making it minimally viable but with 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?

The description mentions retrieving by ID, which aligns with the single parameter 'bank_account_id' in the schema. However, with 0% schema description coverage, the description doesn't add details like ID format or constraints beyond what's implied, resulting in a baseline score due to minimal added value.

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 ('Retrieve') and resource ('a SpherePay bank account by ID'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_customer' or 'get_wallet', which follow a similar pattern, so it doesn't fully distinguish from siblings.

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, such as needing a valid bank account ID, or compare it to sibling tools like 'list_bank_accounts' for broader queries, leaving usage context unclear.

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