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 burden. It successfully discloses the critical behavioral trait that no authentication is required. It implies read-only behavior via 'view/pure', though it could add context about return formats or node query 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?

Two sentences, zero waste. Front-loaded with the action ('Call a view/pure function'), followed by scope ('on a TRON smart contract'), then critical behavioral constraint ('No auth or private key required'). 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?

Given no output schema exists, the description should ideally specify what gets returned (raw hex vs decoded values). While 'view/pure' implies a return value, the format remains ambiguous. The auth clarification compensates partially for missing annotations, but return value documentation is lacking.

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 description coverage is 100% with clear descriptions including examples (e.g., 'balanceOf(address)'). The description adds no parameter-specific semantics beyond the schema, which is appropriate when schema coverage is complete. Baseline 3 applies.

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 specifies 'Call a view/pure function on a TRON smart contract' - clear verb, specific resource, and distinguishes from sibling 'call_contract' by specifying 'view/pure' functions only. The 'No auth' clause further clarifies this is 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?

The phrase 'No auth or private key required' provides implicit guidance to use this for read-only operations versus state-changing alternatives. However, it doesn't explicitly reference sibling 'call_contract' or state when to prefer this over other query tools like 'get_balance'.

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