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

There are no annotations, so the description carries the full behavioral burden. It discloses that the tool creates an invoice and returns a Bitcoin payment link, but it does not mention authorization requirements, side effects on the credit balance, or failure behavior. Partial coverage, but not misleading.

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 short sentences front-load the operation and resource, then immediately give the constraint and return value. Every word is relevant and there is no filler.

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?

For a two-parameter tool with no output schema, the description covers the essential input constraint and the key returned field. It lacks notes on errors, permissions, or post-payment credit application, but the core invocation path is sufficiently specified.

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?

With 0% schema coverage, the description adds meaningful constraint information by restricting 'usd' to the set {2,5,10,20}. However, it does not explain 'api_key' beyond its name, leaving that parameter's semantics mostly to inference.

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 names a specific action and resource: 'Create a BTCPay invoice for credits.' It also states the concrete output ('checkout_link'), which clearly distinguishes it from the sibling tools that deal with inspection, recon, signup, and extraction.

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 phrase 'for credits' implies the intended use case, but the description does not explicitly say when to use this tool versus an alternative or what prerequisites are needed. It relies on inference rather than clear contextual guidance.

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