Taobao Item Card

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

The description goes well beyond the annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false) by detailing return-format degradation (price_cny=None, description_images drift to 0 with meta.warnings), a full error taxonomy (BadRequestError, NotFoundError, challenge_required, TransportDownError, ParserDriftError), and a caching policy ('Only successful cards are cached'). This is rich behavioral disclosure an agent cannot get from the structured fields.

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?

Uses headed sections ('Return Format', 'Error Format') that front-load the purpose then the structured detail, which is easy to parse. It is somewhat verbose for a one-parameter tool, but every sentence carries specific information about return shapes, degradation, and error types without filler.

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 a single required parameter, an output schema, and rich annotations, the description covers the remaining gaps an agent needs: how the response degrades under scraping drift, which errors map to which failure modes, and caching behavior. Nothing essential for correct invocation is missing.

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% and the single parameter already documents 'Item id or item.taobao.com URL' with length bounds. The description adds no further syntax or format guidance for item_id_or_url, so it does not compensate beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Fetch one Taobao item card'), which is clear enough to distinguish from the many sibling *_card and *_search tools. However, it doesn't explicitly contrast with taobao_search or mention that it retrieves a single item by id/URL. Clear but no sibling differentiation beyond the name.

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 (fetch one card by id or URL) but never states when to use this vs taobao_search or other marketplace card tools. No explicit when/when-not guidance or alternative routing is provided, leaving the agent to infer context from the name alone.

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