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

With no annotations, the description carries the full burden and does well: it discloses that payment is on-chain and irreversible, specifies the network (TRON TRC20), the exact-amount requirement, and a 15-minute expiry window. It omits auth/permission requirements and error behavior, but irreversibility and timing are the critical behaviors for this call.

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 sentences, front-loaded with what is created and what is returned, then the payment constraint. Every clause carries information an agent needs; no 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?

There is no output schema and no annotations, yet the description names the return fields (order_id, exact_amount_usdt, pay_to_address) and the payment protocol details. Combined with the fully documented schema, an agent has everything needed to create and pay for an order.

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; each parameter is already documented and the enum values come from the schema. The description reinforces that plan ids come from portvan_catalog and that domain/cid must be verified before payment, but adds no new per-parameter syntax or format detail.

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 states a specific verb and resource ('Create an order for a branded IPFS gateway on your own domain') and immediately names the return payload, distinguishing it from portvan_catalog (plan lookup) and portvan_order_status (tracking). An agent can tell what this does without opening the 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?

It gives a clear operational precondition ('verify domain and cid before paying, then send exactly exact_amount_usdt USDT on TRON (TRC20) within 15 minutes') and points to portvan_catalog as the source of valid plan ids. It never explicitly states when NOT to use it versus the sibling tools, so it stops short of full routing guidance.

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