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 and partially succeeds by documenting the BTCPAY_STORE_ID environment variable fallback and listing specific return fields (currency, speed policy), but omits safety information, error handling, or authorization requirements.

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 uses a clean docstring format with Args and Returns sections that front-load the essential information without unnecessary verbosity, though the structured format is slightly more technical than narrative prose.

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 the tool has only one parameter, an output schema exists, and the description enumerates the specific configuration fields returned, the documentation provides sufficient context for invocation despite missing annotations.

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?

The schema has 0% description coverage, but the description compensates effectively by explaining that store_id is optional and detailing the environment variable fallback mechanism, adding essential semantic meaning missing from the structured schema.

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 description explicitly states 'Get detailed information about a specific BTCPay store' with a clear verb and resource, effectively distinguishing it from sibling list_stores by emphasizing 'specific' and 'detailed information' versus listing operations.

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?

While the description effectively describes what the tool returns, it lacks explicit guidance on when to use this versus list_stores or other retrieval tools, relying instead on implicit differentiation through the 'specific store' phrasing.

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