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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety and external-call profile is covered. The description adds genuine context beyond that: the server checks the confirmed USDT transfer, exact amount, and recipient on-chain, and only returns the URL after confirmation. It omits failure behavior and response shape on mismatch.

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, front-loaded sentences: action, server verification, and outcome. No wasted wording, though the transition between tx hash and order linkage could be sharper.

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 2-parameter verification tool with no output schema, the description covers the core flow and the confirmation condition. It lacks the order_id/tx_hash relationship and post-verification failure behavior, leaving some gaps for an agent handling edge cases.

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 0%, so the schema only supplies types and a hash pattern. The description gives meaning to tx_hash as the payer-provided Polygon transaction hash but does not explain order_id's role or that the hash must match the order's exact amount and recipient — the critical linking semantics.

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 names a specific verb (submit) and resource (payer-provided Polygon transaction hash) and states the outcome (return private report URL after confirmation). It is clearly distinct from siblings such as scan_tls or get_methodology, though it doesn't explicitly reference them.

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?

Usage is implied: call after the payer supplies a Polygon tx hash to unlock a paid report. There are no explicit when-not conditions, no mention that an order must exist first (via create_full_report_order), and no guidance on what to do if verification fails.

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