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

With no annotations, the description carries the full burden. It adds useful context that credentials come from the caller's OpenAny gateway and that charges/authorization are gateway-determined, but it does not disclose whether this is a read-only estimation or a billable action, what happens on invalid input, or what the response looks like.

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?

The description is short and front-loaded, but the first line simply duplicates the title, and the second line is generic gateway boilerplate. It is not bloated, but neither sentence is doing much beyond the structured fields.

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 four-parameter tool with three required inputs and no output schema, the description is too thin. It never explains what is being calculated, how item_ids and target_id affect the estimate, or what the agent should expect back, leaving significant gaps 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 description coverage is 100%, so the input schema already documents all four parameters, including the target_id enum-like meanings. The description adds no additional parameter guidance, which is acceptable given the high schema coverage.

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 is effectively a restatement of the tool title: "DOU+ cost estimation" adds no specificity beyond the name. It does not clarify whether the tool returns an estimated price, a range, or a breakdown, nor does it distinguish this tool from other DOU+ sibling endpoints such as fetch_promotable_item_list or fetch_video_detail.

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?

There is no guidance on when to use this tool versus alternatives. It does not state prerequisites (e.g., needing a valid Douyin web cookie) or the conditions under which a cost estimate is appropriate.

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