TRON infrastructure for AI agents.

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

With no annotations provided, description effectively covers behavioral traits: declares state-changing nature, discloses automatic resource estimation/acquisition via Merx, and specifies auth requirements ('Requires TRON_PRIVATE_KEY and TRON_ADDRESS'). Missing explicit failure modes or confirmation waiting behavior.

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 compact sentences with zero waste: 1) Core purpose, 2) Automatic resource behavior, 3) Prerequisites. Each sentence earns its place and builds necessary context without redundancy. Excellent front-loading of primary function.

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?

Covers execution behavior and auth well, but lacks description of return values or transaction confirmation semantics. For a state-changing blockchain tool without output schema, description should indicate whether it returns tx hashes, receipts, or confirmation status.

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% description coverage, so baseline applies. Description does not add parameter semantics beyond schema (e.g., no examples of ABI-encoding format or guidance on optional vs required context), but schema adequately documents the four parameters including hex encoding note.

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?

Description clearly states specific action ('Execute a state-changing smart contract function') that distinguishes it from sibling tool 'read_contract'. The 'state-changing' modifier explicitly signals this is a write operation, making the purpose unambiguous.

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?

Implies usage context by specifying 'state-changing' (use when modifying state vs reading), and mentions automatic resource handling ('Estimates resources, buys via Merx if needed'). Could be improved by explicitly contrasting with 'read_contract' or stating when NOT to use.

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