Estimate Flash Unstake

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with "nothing is submitted" plus the 404-when-nothing-staked failure mode and public accessibility. It does not discuss snapshot volatility or whether the estimate expires, which would matter for a quote-style 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?

Two tight sentences: the first front-loads what is returned, the second carries the non-mutation and error behavior. No filler and no repetition of the title.

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 an output schema present, return values need no further explanation, and annotations cover the safety profile. The description still supplies the failure mode and the non-submitting guarantee, so nothing needed to call it correctly is missing.

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 coverage is 100%, so the requester pattern and meaning are already documented in the schema. The description adds only that the entire stake is estimated with no filtering options, which is a marginal but real clarification of scope.

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 pairs a specific verb (estimate) with a specific resource (flash unstaking an address's entire staked TRX) and names the outputs the estimate covers. It is clearly distinguishable from siblings like tronsave_get_flash_unstake_request and tronsave_list_flash_unstake_orders, which read existing state rather than projecting a payout.

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?

"Nothing is submitted. Public (any address), read-only" establishes the pre-flight/quote use case, and the 404 condition tells the agent when the call will fail. It stops short of explicitly naming the alternative (e.g., the actual unstake-request tool) or stating when not to call it.

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