taobao_send_reply

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

Discloses that confirm=false returns a preview without sending, while confirm=true sends. Annotations provide no additional behavioral info, so description carries the burden. Additional constraints on message content are given, but no mention of rate limits or error conditions.

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?

Two sentences plus a concise example. Every sentence adds value: purpose, gated behavior, usage restriction. No wasted words.

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 message-sending tool, the description covers purpose, gating logic, language constraint, and provides an example. Output schema exists, so return details are not needed. Complete for the use case.

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 0%, so description fully compensates. The confirm parameter's effect (preview vs send) is detailed, seller and message are explained through example and constraints (Chinese, no international shipping).

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 clearly states the tool sends a Chinese message to a seller and explains the confirm-then-send mechanism. It distinguishes itself from siblings by being the only send-reply tool among the listed Taobao tools.

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?

Provides explicit usage context: messages must be in Chinese, never ask about international shipping. The confirm-then-send pattern is clearly explained. Lacks explicit when-not-to-use or alternatives, but the context is sufficient.

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