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. It discloses key behavioral traits: it creates a resource (implying mutation), specifies HTTPS requirement for the URL, mentions the secret return for verification, and advises to save it. However, it lacks details on permissions, rate limits, or error handling.

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 front-loaded with the core purpose, followed by parameter guidance and return value, all in three efficient sentences with zero wasted words. Each sentence adds critical information.

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 no annotations, 4 parameters with 0% schema coverage, and an output schema present, the description is mostly complete: it covers purpose, parameters, and return behavior. However, it lacks context on prerequisites (e.g., authentication) or error cases, which could be important for a creation tool.

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 meaning by explaining the purpose of each parameter (name, URL as HTTPS endpoint, events with examples and wildcard usage), and notes 'description' is optional (implied by not listing it as required). This goes beyond the bare schema, though it doesn't detail format constraints like URL validation.

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 ('Create a webhook') and resource ('to receive event notifications'), distinguishing it from sibling tools like get_webhook or list_webhooks (which don't exist but get_webhook does). It explicitly defines the purpose beyond just the name.

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 for when to use this tool (to set up event notifications) and includes an example of event types, but does not explicitly state when not to use it or name alternatives among siblings (e.g., get_webhook for retrieving existing webhooks).

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