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

Annotations already indicate read-only, open-world, idempotent, and non-destructive. Description adds return details (attributes, offers with buy URLs, comparison URL, other sources for cross-market new/used price spreads, affiliate disclosure) without contradicting 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 well-structured: starts with purpose and key content, then '언제:' for usage context, and '반환:' for return details. Every sentence adds value; no redundancy. Length is appropriate for the detail provided.

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 simplicity (1 required param, no nested objects, has output schema), the description covers when to use, input source, return structure, and actionable guidance (e.g., using other_sources for price comparison). It fully equips an agent to decide and invoke correctly.

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?

Only one parameter (product_id) with 0% schema coverage. The description provides context that product_id comes from search/recommend results, but doesn't specify format or type beyond the schema's string type. This is sufficient for a single well-understood parameter, though more explicit definition would be ideal.

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 retrieves detailed product info including specs, prices from shopping malls (offers), and cross-comparison of new/used items. It distinguishes from siblings like search_products or compare_products by focusing on a single product deep dive.

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?

Explicitly says when to use: when a user wants to see a product in depth or is about to purchase. Also notes product_id comes from search/recommend results, linking to sibling tools.

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