btcpay-mcp

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

No annotations are provided, so the description carries the full burden. It successfully explains domain semantics (money movement to destinations) but omits operational details like pagination behavior, result limits, or whether this includes pending vs completed payouts. Since an output schema exists, return value description is not required.

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?

Three sentences total with no waste. First sentence establishes the action and scope, second and third provide essential domain context defining what payouts are. Information is front-loaded and 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?

Given zero parameters and the existence of an output schema, the description appropriately focuses on domain explanation. It adequately covers the complexity level of this tool, though could be improved by mentioning if results are filtered by store automatically or if pagination applies.

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?

Zero parameters present. Per evaluation guidelines, zero parameters establishes a baseline of 4. The schema coverage is vacuously 100%, and no additional parameter semantics are needed in the description.

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?

Description opens with specific verb 'List' and resource 'payouts (actual payout transactions)'. The explanation of payouts as 'claims against pull payments' effectively distinguishes this tool from sibling 'list_pull_payments' and 'list_payment_requests' by clarifying the domain relationship.

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 explains the conceptual model (payouts as claims against pull payments), providing implicit context about when to use this versus pull payment tools. However, it lacks explicit when-to-use/when-not-to-use guidance or mention of prerequisites like store selection.

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