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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the closing "Public, read-only" largely restates that. The description still adds real value by defining each status bucket (open orders buyers can take, being paid out, done) and by disclosing that amounts are SUN-scaled and estimateCompletionTime is in seconds.

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?

Three tightly packed sentences, front-loaded with the purpose and closed with a safety signal; nothing is filler. It is slightly dense in the first sentence, with parenthetical glosses stacked for all three kinds, but still readable.

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?

An output schema exists, so return-shape explanation is unnecessary, and pagination is fully covered by the schema. For a simple public list tool the description covers scope, alternatives and units; only ordering of results is left unstated.

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% and the schema already documents kind, limit (default 10, max 50) and offset pagination, so the schema does the heavy lifting. The description only echoes the kind values and adds no format or default detail beyond it; the unit notes it does add concern output fields, not parameters.

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 ("Browse the flash-unstake market") and enumerates the three listable order states with their meaning. It also names the two closest siblings it is not, so an agent can route correctly 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?

"Use to browse the whole market" sets the scope, then explicitly routes the user-specific case to tronsave_get_flash_unstake_request and the preview case to tronsave_estimate_flash_unstake. When-to-use and when-to-use-something-else are both stated.

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