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

Goes beyond the annotations by disclosing that the call spends paymentAmount SUN of the internal balance, requires a wallet-signature identity, and returns one order id per receiver. The non-idempotency note duplicates idempotentHint=false, but the balance spend and auth requirement are genuine additions to a write tool with destructiveHint=false.

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?

Opens with the operation and its distinguishing constraint, then the side effect, then the recommended pre-call workflow. No sentence is filler and the cost warning is placed before the invocation guidance where it matters most.

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?

Covers the high-risk facts an agent needs for a 7-parameter financial batch operation: uniform amount across up to the schema's 50 receivers, balance spend, non-idempotency, signature requirement, and the estimate-first workflow. Return values are already covered by the output schema, so their absence from prose is not a gap.

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% and the schema already documents the per-receiver semantics of resourceAmount and the paymentAmount tolerance formula. The description reinforces that resourceAmount is uniform across all receivers, which is mildly useful, but adds no syntax or format detail beyond the 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?

States a specific verb and resource ("Buy ... ENERGY or BANDWIDTH for several receiver addresses in one call") plus the payment source and return shape (one order id per receiver). The capitalized SAME immediately distinguishes it from per-receiver or single-order purchase siblings like tronsave_internal_order_create.

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 a concrete pre-call workflow: estimate one receiver with tronsave_estimate_buy_resource and show the user receivers, amount and total cost before calling. It never explicitly names the single-address alternative as the fallback for one receiver, so the when-not case is inferred rather than stated.

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