taobao_full_picture

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

The description discloses read-only behavior (matching readOnlyHint) and adds details about unmatched IM threads being flagged as 'unlinked', which goes beyond annotations. It explains the matching policy, providing transparent 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 well-structured with a clear lead sentence, enumerated modes, and a caution. It is concise yet sufficiently detailed, though slightly long due to mode explanations.

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?

The description covers the main functionality (three modes, data joined, matching behavior). Despite not detailing output fields, the presence of an output schema mitigates this omission. It provides adequate context for a complex tool.

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 description coverage, the description adds significant meaning by explaining each parameter's function: `seller` returns a vendor dossier, `order_id` joins order with tracking and thread, and omitting both gives an overview. Examples further clarify usage.

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 joins cart, orders, tracking, and seller chats by vendor. It distinguishes three usage modes (seller, order_id, none), providing a specific verb ('joins') and resource ('data by vendor'). This clarity differentiates it from sibling 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?

The description implies usage through the three modes (e.g., 'use `seller` for a vendor dossier') but does not explicitly contrast this tool with alternatives like taobao_search or taobao_track_orders. No guidance on when not to use it.

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