TRON infrastructure for AI agents.

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

No annotations are provided, so the description must carry full disclosure burden. It mentions the authentication requirement but omits critical behavioral traits: that the operation is irreversible, consumes gas fees, requires sufficient TRX for bandwidth, may fail due to slippage or liquidity, and returns transaction details.

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?

Two sentences with zero redundancy. The first identifies the operation and platform; the second states the critical prerequisite. Every word 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?

For a high-stakes DeFi mutation with no output schema and no annotations, the description is insufficient. It lacks warnings about financial risk, irreversibility, gas costs, expected return values (transaction hash?), and failure modes essential for an agent to safely invoke this tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds minimal parameter-related context—primarily noting the external TRON_PRIVATE_KEY requirement (not in schema)—but does not clarify parameter formats (e.g., whether amount is in base units or decimal) or slippage calculation specifics.

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 clearly states the specific action (execute), resource (token swap), and platform (SunSwap V2). However, it does not explicitly differentiate from the sibling tool `get_swap_quote`, which agents might confuse as the execution step versus the quoting step.

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?

While it notes the prerequisite 'Requires TRON_PRIVATE_KEY', it fails to provide workflow guidance such as when to use this versus `get_swap_quote` (get price first) or `approve_trc20` (required approval before swapping TRC20 tokens). No exclusions or alternatives are mentioned.

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