btcpay-mcp

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

No annotations provided, so description carries full burden. It discloses return structure (amounts, confirmations, statuses) but omits safety properties (read-only status), error handling, pagination behavior, or rate limits despite being a financial data tool.

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 Args/Returns format that efficiently organizes information. Front-loaded with clear purpose statement. Slightly redundant with schema structure but necessary given empty schema descriptions.

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?

Adequate for a single-parameter tool with existing output schema. Covers parameter semantics and return value fields, but omits error scenarios (invalid payment_method_id), pagination limits, or maximum date ranges that would be necessary for robust agent usage.

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?

Excellent compensation for 0% schema description coverage. Provides concrete example ('BTC') and explains default behavior when empty, which the JSON schema only indicates as empty string default without semantic meaning.

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) + resource (on-chain wallet transactions) + scope (for a payment method). Clearly distinguishes from siblings like list_invoices or get_wallet_balance by specifying 'wallet transactions' and 'on-chain' (implying blockchain vs Lightning).

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?

Provides parameter default guidance ('Leave empty to use BTC by default') but lacks comparative guidance on when to use this vs alternatives like get_wallet_balance or list_payouts. No mention of prerequisites or conditions.

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