TRON infrastructure for AI agents.

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

Reveals executes on-chain TRX transfer and includes verification logic, hinting at async/blockchain behavior. However, missing critical mutation details: transaction fees, irreversibility, required confirmations, failure modes, or idempotency—especially important given zero annotations.

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?

Single sentence, nine words, zero redundancy. Action verb front-loaded. Every element earns its 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?

Minimal parameter complexity (1 param) and no output schema reduce burden, but as a financial mutation tool, the description omits essential operational context like cost implications, authorization scope, or balance requirements that would aid agent decision-making.

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 has 100% coverage (invoice_id described as 'Invoice ID to pay'), establishing baseline 3. Description adds no additional semantic context about ID format, source, or constraints beyond 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?

States specific action (Pay), resource type (x402 invoice), and mechanism (sending TRX and verifying payment). Distinguishes from generic transfer tools via 'x402' specificity and verification step. Minor gap: assumes familiarity with 'x402' protocol without brief context.

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?

No guidance on when to select this versus sibling tools like 'create_order', 'deposit_trx', or 'transfer_trx'. Does not indicate prerequisites (e.g., TRX balance requirements) or when payment workflows should use this specific endpoint.

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