btcpay-mcp

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

With no annotations provided, the description carries the full burden; it successfully discloses that the tool returns a payment request ID and link, but omits other behavioral traits such as idempotency, error conditions, whether the link is active immediately, or required permissions.

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 employs a clear docstring structure with Args and Returns sections that efficiently organize information without redundancy, though the format is slightly more verbose than a pure narrative style.

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?

Despite six parameters and zero schema descriptions, the description successfully documents every parameter plus the return value, providing complete invocation context; the presence of an output schema means the brief return value mention is sufficient.

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?

Given 0% schema description coverage, the description fully compensates by documenting all 6 parameters with semantic meaning, including concrete examples ('0.001', 'BTC', 'USD') and clarifying special values (0 = no expiry) that the schema lacks.

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 opening sentence 'Create a new payment request (reusable payment link)' provides a specific verb and resource, while the parenthetical effectively distinguishes this tool from siblings like create_invoice (typically one-time) and create_pull_payment (different funding mechanism).

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 identifies the output as a 'reusable payment link,' implying its use case, but it does not explicitly state when to use this tool versus alternatives like create_invoice or create_pull_payment, nor does it mention prerequisites or conditions for use.

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