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. Discloses validation, simulation behavior, and cost estimation features. Also notes auth requirement. Lacks critical details for a financial execution tool: atomicity guarantees (all-or-nothing execution?), error handling, and side effects on partial failure.

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 well-structured sentences: purpose first, behavioral features second, requirements third. No redundancy. Front-loaded with action verb. Minor quibble: 'etc.' is vague, but overall efficient.

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?

Minimum viable for a complex financial orchestration tool. With 100% schema coverage and no output schema, description covers essentials (purpose, validation, auth). However, given complexity of multi-step blockchain operations, gaps remain regarding return value structure, step failure behavior, and interaction with sibling transaction tools.

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 with clear parameter definitions. Description adds value by connecting 'simulates' to dry_run behavior and 'resource cost estimates' to resource_strategy, but primarily reinforces what the schema already documents. Baseline 3 appropriate given comprehensive 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 'Execute' and resource 'multi-step operation' with concrete examples (transfer, swap, buy resources) that distinguish it from single-step siblings like transfer_trx or execute_swap. The 'multi-step' qualifier effectively differentiates its orchestration role.

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 prerequisite ('Auth required') and implies usage through 'multi-step' capability, suggesting when to use it (complex workflows). However, lacks explicit guidance on when to prefer specific tools (execute_swap, transfer_trc20) versus this orchestration tool, or when to use dry_run mode.

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