My Flash Unstake Request

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

Annotations already declare readOnly, idempotent, and openWorld. The description adds useful behavioral context beyond that: the response includes request state, payout state, amounts and release progress, and `request` is null when none exists. It also notes the authentication requirement, which is not captured in the 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?

Two sentences, both front-loaded and information-dense. The core purpose, response contents, null case, auth requirement, and read-only nature are all communicated without any filler.

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?

Given the zero-parameter schema, existing output schema, and annotations covering safety/idempotency, the description is complete. It adds the essential auth prerequisite, clarifies the null case, and summarizes returned fields relevant to the user's decision. No material gaps remain.

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?

The tool has zero parameters, so the baseline is 4. The description correctly adds no parameter detail and instead focuses on response semantics and auth requirements.

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 ('Read') and resource ('the logged-in user's flash-unstake request') and explains the concept (selling staked TRX early for immediate payout). It is clear what is returned, but it does not explicitly name the sibling `tronsave_list_flash_unstake_orders` to delineate the single-request vs. list distinction.

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?

Provides a prerequisite ('Requires a wallet signature identity') and the read-only nature, which implies when it can be used. However, it does not state when to prefer this over alternatives like `tronsave_list_flash_unstake_orders` or `tronsave_estimate_flash_unstake`, nor any explicit exclusions.

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