Estimate TRX Cost Before Order

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds real context on top: the auth model (internal API key via tronsave_login or Authorization header), the rule never to pass keys as tool arguments, and the ~3-second price volatility. That volatility detail is decision-relevant behavior an agent could not infer from 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?

Front-loaded with purpose, then auth, then usage, then a clearly labelled FRESHNESS block. Dense but nearly every sentence carries operational weight; the auth paragraph is slightly verbose relative to the rest.

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 7-parameter read-only estimate with a full output schema, the description covers what an agent needs: auth prerequisites, purpose, downstream handoff, and price staleness. The only gap is not stating how it differs from the non-internal tronsave_estimate_buy_resource.

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 every parameter including enums, defaults, and the nested options object is already documented in the schema. The description only reinforces unitPrice via the freshness note and adds nothing about resourceAmount, durationSec, or the partial-fill flag — baseline 3 is appropriate.

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 and resource — estimate TRX cost and availability for a buy order — and qualifies it as the api-key internal-account variant, which separates it from the public estimate siblings. It also names the downstream tool (tronsave_internal_order_create) the result feeds into.

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?

Explicit when-to-use ('quote or price check') plus a concrete workflow rule: re-estimate immediately before creating the order because unitPrice/estimateTrx refresh roughly every 3 seconds. It does not explicitly exclude the sibling tronsave_estimate_buy_resource, so the alternative is only implied by the 'internal account' qualifier.

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