prepare_transactions_tron

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

No annotations are provided, so the description carries the burden; it discloses that the output is unsigned, returns fee details, and incurs per-action credit costs. It does not state auth/permission requirements, whether the call has side effects on-chain, or rate limits, which is a moderate gap for a no-annotation 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?

Front-loaded first sentence states the core purpose, then a flow sentence, then a scannable action/credit list. The credits disclaimer is slightly verbose but earns its place by warning costs may change.

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?

With no output schema and no annotations, the description covers the purpose, the return shape at a high level (unsigned tx + fee details), the follow-up calls, and per-action costs. Missing auth and side-effect details keep it from being fully complete, but it is adequate for a 9-param builder tool.

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%, so the per-parameter meaning (amount units, sender/recipient, contract, tokenId, feeLimit) is already documented. The description adds the action enumeration with credit costs, which is marginal value beyond the schema enum.

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?

States a specific verb (build/prepare) and resource (unsigned Tron transactions) and explicitly distinguishes itself from the generic EVM prepare endpoints used for other chains. The three action bullets make the scope concrete, so an agent can tell it apart from the sibling prepare_transactions_* tools.

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?

Gives an explicit downstream flow: prepare, then sign locally with tron_sign, then broadcast via broadcast_signed_transaction. It also names the alternative (generic EVM endpoints) and the condition (other chains), leaving little to inference.

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