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

With no annotations, the description carries the full burden, and it does disclose meaningful payment routing (single transfer, 100% to the owner address, no split or commission). However, it omits permission/auth requirements, whether buyer_wallet is optional or what happens when it is omitted, invoice expiry, and any idempotency or post-creation behavior.

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 tight sentences, front-loaded with the action and the routing guarantee; no filler. Minor jargon ("HOBO Works owner address") slightly reduces immediate clarity.

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?

No output schema, no annotations, and 0% parameter description coverage, so the description must do more than it does. It never tells the agent what creation returns (invoice ID, payment address/amount) or how the resulting invoice is verified or paid.

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?

Schema description coverage is 0% across three parameters (product_id, asset_id, buyer_wallet), and the description compensates for none of them beyond hinting that asset_id encodes a network. product_id and buyer_wallet semantics are entirely undocumented.

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 a specific verb and resource: "Create a fixed-price crypto invoice on a supported network." An agent can tell what it does, but it never distinguishes itself from the sibling create_usdc_invoice (also crypto) or create_stripe_checkout, so the boundary is left to inference.

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?

No when-to-use or when-not-to-use guidance. There are three overlapping create_*_checkout/invoice siblings, yet the description never says which one applies when; "on a supported network" only vaguely implies multi-chain scope.

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