TRON infrastructure for AI agents.

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

No annotations provided, so description carries full burden. Adds critical safety context: 'Signs and broadcasts on-chain' indicates permanent state change, and 'Requires TRON_PRIVATE_KEY' warns of credential need. Lacks details on return values, gas costs, or reversibility (can be overridden by subsequent approvals).

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 sentences, zero waste. Front-loaded with action ('Approve...'), followed by behavioral trait ('Signs...'), then prerequisite ('Requires...'). 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?

Adequate for basic invocation but incomplete for a financial mutation tool: missing return value description (transaction hash?), gas fee implications, and reversibility notes. No output schema exists to compensate.

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%, establishing baseline 3. Description term 'spending allowance' conceptually maps to the parameters (token, spender, amount) but adds no syntax, format, or example details beyond what the schema already provides.

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?

Specific verb 'Approve' with clear resource 'TRC-20 spending allowance'. Distinct from sibling 'transfer_trc20' (which moves tokens) and 'get_trc20_balance' (read-only).

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?

Provides critical prerequisite ('Requires TRON_PRIVATE_KEY') but lacks explicit when-to-use guidance vs alternatives (e.g., when to approve vs immediate transfer, or that this is typically needed before execute_swap). Usage is implied by 'spending allowance' terminology.

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