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

The description adds substantial behavioral context beyond the annotations: on-chain verification rules, screening behavior, pending and rejected states, specific rejection reasons, tx_already_used handling, and Solana payer constraints. It is consistent with the annotations and gives the agent a rich picture of what happens on success and failure.

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 core action is front-loaded and the dense error-code details are relevant to correct invocation. The single-paragraph format is somewhat run-on, but most sentences carry useful operational information.

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 complex payment-reporting tool with no output schema, the description covers success behavior, retry conditions, error codes, Solana-specific requirements, and the receiver analysis result. It gives enough context for an agent to call and interpret the tool correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for txHash and especially payer on Solana, including the requirement that the transaction be signed by that payer. It does not add much beyond the schema for id, but overall it improves parameter understanding.

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 action and resource: reporting an analysis payment transaction to the server after it is mined, with on-chain verification details. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as invoice_analysis_pay or invoice_report_payment.

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 clearly says to call once the transaction is mined and to retry after a few seconds when the payment is pending. It also explains error conditions, but it does not explicitly name when to use this tool versus related siblings like invoice_analysis_pay.

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