taobao_export_inventory

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

Beyond the false annotations, the description discloses that it pages through order lists, computes costs, and caches results. It explains resource usage for 'refresh=false' and image embedding details, adding significant behavioral context.

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 front-loaded with the purpose and includes detailed functionality, parameter explanations, and an example. It is informative but slightly lengthy, though every sentence adds value.

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?

Given the tool's complexity and lack of schema descriptions, the description provides a thorough overview of functionality, output format, parameter effects, and edge cases (cache, excluded orders). It is complete.

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?

With 0% schema coverage, the description adds meaning for 'since', 'refresh', and 'embed_images' via detailed explanations and an example. However, 'filename' is not mentioned, leaving a gap.

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 exports purchase history into a visual inventory workbook with landed cost, listing columns and sheets. However, it does not explicitly distinguish itself from the sibling tool 'taobao_export_xlsx'.

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?

The description provides usage context, such as paging behavior with 'since', caching with 'refresh', and that food orders are excluded. It does not specify when not to use or mention alternatives.

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