Amazonで家具・収納商品を検索（URL生成）

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns a URL only, not product data, and that SearchIndex is auto-selected. It also instructs presenting the URL. However, it does not mention potential error cases or behavior for invalid parameters, which would add more transparency. Overall, good but not exhaustive.

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 three concise sentences: when to use, what it does (URL generation, no data), and an instruction. No filler, front-loaded purpose. Every sentence contributes meaning.

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 essential purpose, usage context, and expected output (affiliate_url), which is sufficient for selecting and invoking the tool. However, it does not mention that the tool is specifically for furniture/storage products (though the title does), and it lacks edge-case guidance for empty search results. Minor gaps but overall 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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds context about SearchIndex auto-selection from category, but does not explain sort or price parameters beyond the schema. It does not need to repeat schema details, so it meets the baseline.

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 generates an affiliate URL for Amazon search results and explicitly notes it does not return product data. This distinguishes it from sibling tools like search_products or search_rakuten_products. The verb 'generate' and resource 'Amazon search results page URL' are specific.

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 when to use this tool: 'when the user wants to buy on Amazon or when not found on Rakuten'. It also provides an alternative (Rakuten) and instructs to present the affiliate_url to the user. This is clear guidance for selection and invocation.

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