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 a key behavior: the invoice yields two direct USDC transfers (75% seller / 25% HOBO) with no splitter contract. It omits auth requirements, idempotency, and any per-chain differences, leaving meaningful gaps.

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 short sentences, front-loaded with the action and asset, with no filler. The split detail and the 'no splitter contract' note both earn their 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?

There is no output schema, so the description correctly covers the return behavior (the two-transfer payout structure). It is nearly complete for a creation tool, missing only auth/prerequisite context.

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%, so the description must compensate. It explains buyer_wallet's purpose conditionally and restates the chain enum, but leaves product_id entirely undefined, so compensation is only partial.

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 USDC invoice,' reinforced by the supported chains. It is clearly distinguishable from create_stripe_checkout by asset, but it never names that sibling to make the routing explicit.

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?

Gives one conditional usage rule ('For an agent seller, provide buyer_wallet'), which is real guidance. However, it offers no when-to-use vs. when-not-to-use direction against sibling payment tools like create_stripe_checkout or verify_usdc_payment.

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