btcpay-mcp

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

No annotations provided, so description carries full disclosure burden. It adds valuable domain context that payment requests 'generate invoices on demand' and are 'persistent', but omits operational details like pagination behavior, result limits, or explicit read-only safety confirmation.

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?

Two efficiently structured sentences with zero redundancy. The first sentence states the action; the second provides essential domain context. Every sentence earns its place.

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?

Sufficient for a zero-parameter list operation with an output schema available. Explains the critical distinction between payment requests and invoices, but could improve by noting pagination behavior or if the list includes archived items.

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?

Input schema contains zero parameters, meeting the baseline requirement. No parameter documentation is needed.

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?

Uses specific verb 'List' with clear resource 'payment requests' scoped to 'the store'. Parenthetical '(reusable payment links)' effectively distinguishes from siblings like list_invoices and create_invoice.

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?

Explains payment requests are 'persistent' and useful for 'recurring billing, tipping, and donations', implying when to use versus one-time invoices. However, it does not explicitly name alternative tools like list_invoices or create_payment_request.

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