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

No annotations are provided, so the description must carry the full behavioral burden. It usefully states 'This server never holds funds or secrets' and explains the payer sends NOID to the merchant address, but it omits idempotency, authentication needs, return behavior, webhook behavior, and expiration/confirmation semantics.

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 two short sentences with the purpose front-loaded and no filler. It is highly efficient, even though its brevity contributes to gaps assessed in other dimensions.

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 an 8-parameter invoice-creation mutation with no annotations and no output schema, the description is too sparse. It gives purpose and a non-custodial trust signal, but not enough detail to confidently invoke the tool with the correct parameter meanings and expected behavior.

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% for 8 parameters, so the description needs to compensate but largely does not. It loosely connects 'MERCHANT o1 address' to merchant_address, but leaves usd, amount_micronoid, quote_id, memo, webhook_url, expires_in_seconds, and required_confirmations unexplained.

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 uses a specific verb and resource, 'Create a checkout invoice,' so the agent can distinguish creation from siblings like list_invoices or check_invoice. It does not explicitly name alternatives or define terms such as 'NOID' or 'o1 address,' but the core action is clear.

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?

There is no explicit guidance on when to use this tool versus get_quote, claim_payment, check_invoice, or other siblings. The only usage signal is implicit in the phrase 'checkout invoice,' with no prerequisites or exclusions stated.

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