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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds context about the return structure (seed, items with slots, styling_reason, affiliate_disclosure) and advises using get_product_image for photos. 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 very concise: three short paragraphs. The first sentence states the purpose, the second provides usage guidelines, the third describes parameters and returns. Every sentence adds value with no redundancy.

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 moderate complexity and the presence of output schema and good annotations, the description covers essential aspects: input requirements, output structure, and a practical note about using get_product_image. It is complete for an agent to select and invoke the tool 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?

With 0% schema description coverage, the description explains each parameter: product_id (seed item, optional), intent (intent/mood, optional), budget (total budget upper limit, optional), and the constraint that at least one of product_id or intent is required. It does not specify possible intent values or format, but the explanation adds significant meaning.

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 explicitly states the tool's purpose: recommending suitable outfit coordination based on seed product or intent. It distinguishes from sibling tools like 'recommend_products' by focusing on full outfit compositions (한 벌 구성). The specific verb 'recommend' and resource 'outfit coordination' are clear.

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 provides clear when-to-use scenarios with examples ('이 코트에 어울리는 코디', '가을 데이트룩 코디') and states that at least one of product_id or intent is needed. However, it does not explicitly mention when not to use this tool or suggest alternatives like 'recommend_products' for single items.

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