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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is paid, the price, the network, the x402 protocol, and the endpoint URL, but it does not describe return shape, error behavior, or validation characteristics.

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 is short and front-loads the operation before payment details. The "args: i" fragment is terse and somewhat unclear, but overall there is little wasted text.

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 simple decoder with no output schema, the description covers the operation and payment requirement but omits what the decoded result contains or how failures appear. That leaves a noticeable contextual gap for an agent invoking the tool.

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 indicates zero required parameters and 100% schema description coverage, so the baseline is 4. The description adds a cryptic "args: i" reference, which signals an input argument but does not clearly define its meaning or format.

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 states a specific verb and resource: "Decode a Lightning BOLT11 invoice." This is clearly distinguishable from sibling utilities like base64, hash, nip19, slug, timeconv, urlparse, and uuid, which operate on different inputs.

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 implies the tool is used when decoding a BOLT11 invoice and discloses the payment prerequisite (0.001 USDC on Base via x402). However, it gives no explicit when-not-to-use guidance or alternatives, though none of the listed siblings are close substitutes.

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