Get Minimum Unit Price

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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds useful disclosure: no login required, GraphQL source `market.estimateMinPrice`, return shape `{ minPrice }`, and unit semantics that vary with `durationSec`.

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 dense sentences front-load the purpose, return value, source, and alternatives. There is no filler, and the most decision-relevant information appears first.

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 values need not be fully documented. The description covers auth, idempotency, source, unit semantics, optional address behavior, and how it relates to sibling tools, making it complete for correct invocation.

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 baseline is 3. The description still adds meaning beyond the schema by explaining that the returned price is in SUN per resource unit, becomes per-day when `durationSec` >= 86400, and that `address` only scopes context when supported by the API.

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 uses the specific verb 'Quote' with the resource 'minimum unit price for a buy,' and explicitly distinguishes this tool from `tronsave_estimate_buy_resource` and `tronsave_list_order_books` by stating their complementary purposes.

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?

It clearly routes the agent toward sibling tools for full buy quotes and order-book depth, implying this tool is for the narrower minimum-price quote. However, it does not explicitly state exclusion conditions such as when not to use it or whether it is a prerequisite for a buy flow.

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