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 full burden and discloses critical behaviors: session-scoped storage, automatic address derivation, and the security guarantee that the key stays local and is never sent to Merx servers. It could improve by mentioning validation behavior or error handling.

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?

Four tight sentences covering purpose, side effects (address derivation), enabled capabilities, and security guarantees. Every sentence earns its place with zero redundancy. Information is front-loaded with the primary action.

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 the high complexity (cryptographic key handling) and lack of annotations/output schema, the description provides adequate behavioral context and security disclosures. Minor gap: does not describe return values or confirmation behavior, though the side effects are well-documented.

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?

The input schema has 100% description coverage ('Your TRON private key (64 hex characters)'). The description adds no additional parameter-specific guidance beyond what the schema already provides, warranting the baseline score of 3.

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 (Set), resource (TRON private key), and scope (for this session). It distinguishes from sibling 'set_api_key' by specifying 'TRON private key' and distinguishes from read operations by listing specific write tools it enables.

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?

It explicitly lists the write tools this enables (transfer_trx, transfer_trc20, etc.), providing clear context for when to use it. However, it lacks explicit 'when not to use' guidance or comparison to alternatives like set_api_key for authentication.

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