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

Annotations already disclose the safety profile, and the description adds non-obvious behavior: the $0.005 per-call cost, the x402 PaymentRequired challenge/retry flow, and the HTTP equivalent endpoint. It does not explain the readOnlyHint=false implication or the response shape, but it adds substantial operational context beyond annotations.

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 is front-loaded with the purpose, then covers cost/payment mechanics and the HTTP equivalent in compact sentences. Every sentence adds useful information for invoking a paid estimator correctly.

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?

Purpose and payment flow are covered, but there is no output schema and the description says nothing about the estimate response. It also leaves ambiguous which of the five parameters are actually required, since the schema lists none as required.

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 baseline is 3 even without parameter details in the description. The description adds only general context about USDT transfers and does not clarify units, requiredness, or the optional contract_call and trx_balance_sun parameters.

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 a specific verb and resource: estimate TRON energy/bandwidth needed for a USDT transfer. That is clear enough for an agent to understand the tool's function, though it does not explicitly distinguish it from nearby fee/estimate siblings.

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 gives a clear use case (USDT transfer on TRON) and payment invocation flow, but does not say when to use this versus alternatives such as fees_estimate or fee_oracle_recipe. Usage is implied rather than explicitly scoped.

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