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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing the auth requirement (wallet signature identity) and the empty-state contract ('request is null when there is none'). It does not cover what happens without a valid signature (error vs. empty), which keeps it just short of a 5.

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: the first defines the resource and its returned facets, the second routes the agent to alternatives and states the precondition. Every clause carries information; there is no restatement of the title or name.

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, the description need not explain return shapes, and it still flags the key empty case. Auth requirement, read-only nature, and sibling routing are all covered, which is everything an agent needs to call this correctly.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words re-documenting an empty 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 ('Read the logged-in user's flash-unstake request') and enumerates the returned facets (state, payout state, amounts, release progress). The parenthetical explains what a flash-unstake actually is, and the description explicitly excludes the sibling tools that cover previewing and browsing, so the agent can pick it without opening a schema.

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 an explicit when-to-use rule ('the user's own request') and names two concrete alternatives with the conditions that select them: tronsave_estimate_flash_unstake for previewing a payout, tronsave_list_flash_unstake_orders for browsing all orders. It also states a precondition (wallet signature identity), leaving nothing to inference.

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