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 of behavioral disclosure but only reveals the authentication requirement ('No auth required'). It fails to disclose whether this is a read-only operation, what data structure the quote returns, rate limits, or quote expiration 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?

The description consists of two efficient sentences with zero waste. The core purpose ('Get a real swap quote from SunSwap V2') is front-loaded, while the constraint ('No auth required') follows as essential secondary information.

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?

For a DeFi quoting tool with 4 parameters and no output schema or annotations, the description is inadequate. It fails to describe what the quote contains (price, route, minimum output, deadline) or its relationship to 'execute_swap,' which is critical for agent workflow completion.

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, documenting all four parameters including token symbols and slippage tolerance. The description adds no additional parameter semantics (such as valid token formats or amount precision), but the comprehensive schema makes this acceptable at baseline level.

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 states the specific action ('Get'), resource ('swap quote'), and source system ('SunSwap V2'), distinguishing it from generic price tools. However, it does not explicitly differentiate from siblings like 'get_best_price' or 'analyze_prices' that may also provide pricing information.

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 description notes 'No auth required,' which indicates a usage constraint, but provides no guidance on when to use this versus 'execute_swap' (which performs the actual swap) or versus 'simulate.' It lacks prerequisites or workflow context for the quoting process.

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