TRON infrastructure for AI agents.

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

With no annotations provided, the description carries the full disclosure burden. It successfully notes the MERX_API_KEY requirement (auth behavior) and implies read access via 'Get', but omits output format details, rate limits, and explicit safety confirmation that would be necessary for a mutation tool.

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 waste. First sentence establishes action and scope (including specific currencies); second states prerequisites. Information is front-loaded and appropriately sized.

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 a simple read operation but has clear gaps: no output schema exists (common for this tool type), and with numerous sibling balance-related tools (get_trx_balance, get_trc20_balance, get_account_info), the description should clarify the specific use case or return structure differences.

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?

Zero parameters justifies the baseline score of 4. The description adds value by noting the MERX_API_KEY requirement, which indicates external configuration is needed despite no input parameters being defined in the 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?

Clear verb 'Get' and resource 'Merx account balance' with specific assets (TRX, USDT, locked) mentioned. The 'Merx account' and 'locked' status implicitly distinguish it from siblings like get_trx_balance and get_trc20_balance, though explicit contrast would strengthen this to a 5.

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?

States the prerequisite 'Requires MERX_API_KEY' which is critical usage context given the empty parameter schema. However, lacks explicit guidance on when to use this versus sibling tools like get_trx_balance, get_trc20_balance, or get_account_info which appear to serve similar purposes.

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