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

Annotations already declare readOnlyHint and idempotentHint, but the description adds material behavior beyond them: required internal API key, the fact that keys are never passed as arguments and are forwarded from the session/header, and the roughly 3-second price volatility requiring re-estimation before order creation.

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?

Front-loaded with purpose, then auth, then routing, then a labeled FRESHNESS caveat, so an agent can stop reading early. It is dense with parentheticals (api-key mode, signature mode) that could be trimmed, but every sentence carries actionable information.

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?

For a 7-parameter read-only estimation tool with a full schema and an output schema, the description covers the remaining unknowns: auth path, no-key-in-arguments rule, sibling routing, and quote staleness. 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 baseline is 3; the description nonetheless adds that unitPrice and estimateTrx are live values that shift about every 3 seconds, which is temporal meaning the schema does not convey. Other parameters (receiver, requester, durationSec, resourceType, options) are left entirely to the 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: estimate TRX cost and availability for a buy order before submission. It also scopes the account type (internal api-key account) and explicitly distinguishes itself from tronsave_estimate_buy_resource, which serves tronsave_create_order quotes.

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 explicit when-to-use (user wants a quote or price check), the downstream step (feed the result into tronsave_internal_order_create), and an explicit when-not with the correct alternative (tronsave_estimate_buy_resource for tronsave_create_order).

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