alibaba_supplier_search

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

The description complements the readOnlyHint annotation by adding behavioral details: it returns only text, no price or photos, and the user must click for more info. No contradictions with 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?

The description is a single sentence plus a clarifying note. It is front-loaded with the main action and efficient, with 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?

Given no output schema, the description adequately explains what the tool returns (title, rating, snippet, link) and what it does not. It could mention pagination or result limits, but for a search tool, it is sufficiently 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?

The input schema already provides a clear description for the 'query' parameter. The description adds useful context: query should be a product/OEM query, brand-free for private label. This adds meaning beyond the schema, though schema coverage is high.

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 finds Alibaba supplier/manufacturer listings for a query via Serper site:alibaba.com, and specifies the return fields (title, rating, snippet, link). It distinguishes from other tools by highlighting its text-only nature and the absence of price/photo.

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 explicitly says 'TEXT ONLY: no price or photo available via this source (the user sees price / MOQ / photos on Alibaba after clicking).' This tells the agent when to use this tool (when text info suffices) and when not to (if price/photo needed, use another method), providing clear usage boundaries.

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