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

No annotations are provided, so the description carries the full burden. It usefully discloses automatic on-chain verification and status transitions to paid or payment_review while confirmations accumulate, but it does not cover permission/auth needs, failure handling, or the request_manual_review path beyond what the schema says.

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 dense sentences and front-loads the key point that this is an optional shortcut. It has some redundancy with schema enums, but no major bloat.

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?

Given no annotations, no output schema, and six parameters with low schema coverage, the description covers the verification lifecycle well but leaves important context unexplained, especially required order_id and note/manual-review 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 only 17%, so the description must compensate. It explains chain, tx_hash, and the evm-only network condition, but omits the required order_id and the note parameter, and largely repeats enum values already present in the schema.

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: submitting a crypto transaction proof after sending the exact amount due. It clearly distinguishes this optional shortcut from automatic crypto payment detection and names verify_crypto_payment as the follow-up sibling.

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?

It explicitly says this is an optional shortcut because crypto payments are detected automatically, gives the precondition of sending EXACTLY next_action.amount_due, and says to call verify_crypto_payment when status is payment_review. It does not state hard exclusions beyond the optional nature, so it is strong but not fully exhaustive.

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