btcpay-mcp

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

No annotations provided, so description carries full burden. It successfully discloses the env var fallback mechanism and return value structure (on-chain vs Lightning, connection status). Does not explicitly state read-only nature or error cases, though 'List' implies safety.

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?

Uses structured Google-style docstring format (Args/Returns). Three concise sentences with zero redundancy; front-loaded purpose followed by parameter and return details.

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?

Appropriate for a single-parameter read operation. Describes return content despite presence of output schema, adding value by clarifying the specific data types (BTC, LTC, Lightning) and status fields included.

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 coverage is 0% (no descriptions in properties). Description fully compensates by explaining store_id semantics, optionality, and the empty-string default behavior tied to environment variable resolution.

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?

States specific verb (List) and resource (payment methods enabled for a BTCPay store). Clear scope, though it does not explicitly contrast with sibling 'get_store_info' to prevent confusion.

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?

Documents the environment variable fallback behavior (BTCPAY_STORE_ID) which guides usage when store_id is omitted. However, lacks explicit guidance on when to use this versus creating invoices or checking wallet balances.

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