숙소 검색

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

No annotations are provided, so the description carries full burden. It discloses a key side effect: results are automatically saved as DB snapshots for later price_history. However, it omits other behavioral details such as rate limits, pagination behavior, or return format, which are important for a web-scraping tool.

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?

Two sentences, front-loaded with the core action and resource. The second sentence provides usage trigger and side effect. No redundancy or 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?

No output schema exists, so the description must explain return values. It only says '숙소 목록' (accommodation list) without specifying fields like price, rating, or URL. Given the tool's complexity and lack of output schema, this is a significant gap for an agent to correctly present or process results.

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 description coverage is 100%, so baseline is 3. The description adds no param information beyond the schema, which already richly documents region conversion, overrides, and per-site fields. The description's mention of '지역·날짜·인원' only paraphrases existing schema content.

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 fetches accommodation lists for a specific region/date/person count from Airbnb and Yanolja. It includes a specific verb '가져옵니다' (fetches) and a clear resource. It also distinguishes from siblings by mentioning the snapshot saving that feeds into price_history.

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 states when to call: when the user mentions travel dates and region and says '숙소 찾아줘' or '어디가 싼지 알려줘'. Provides context but does not explicitly exclude alternatives like compare_prices, though sibling names imply their roles.

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