Taobao Search

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

Goes well beyond annotations by disclosing dependency on Chrome/CDP, login wall behavior, and the significant 'price_cny None when hidden — never 0' output nuance. Also details error conditions (TransportDownError, ParserDriftError) that are not in annotations.

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?

Well-structured and concise. The core purpose is stated in the opening sentence, followed by organized return format and error format sections. Every sentence contributes useful information without redundancy.

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?

Despite having a full output schema and strong annotations, the description adds crucial operational context: Chrome rendering dependency, login requirements, error conditions, and output quirks. This makes the tool safe and correctly invocable even with the schema and annotations present.

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% with clear descriptions for both parameters, so the description need not add parameter-level detail. The return format section adds output context but does not enhance parameter semantics beyond what the schema provides.

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's purpose: 'Search Taobao listings' with the distinctive detail that it is 'rendered in the operator's Chrome.' This distinguishes it from sibling tools like taobao_card and other marketplace searches.

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 clear context for use (searching Taobao, requires operator's Chrome, login wall handling) but does not explicitly mention alternatives or when-not-to-use. The error section implies prerequisites (log into taobao.com) and retry guidance.

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