가격 분포 비교

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a key behavioral trait: normalizing both sites' display standards (total vs per-night) to per-night prices. However, it does not mention whether this is a read-only operation, any rate limits, or output format, which are important for an unannotated 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?

The description is three sentences, front-loaded with purpose, then usage, then normalization detail. Every sentence contributes meaningful information with no fluff or repetition.

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 tool has 8 parameters, 3 required, and no output schema. The description covers purpose, usage, and normalization, and even hints at output content (median, quartiles, by type). However, it lacks an explicit description of the return format or possible errors, which would be more critical given the absence of an output schema.

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 coverage is 88%, so most parameters are already documented in the schema. The description does not add significant param-specific semantics; it only implies 'same conditions' anchoring to region, checkin, and checkout. The undocumented maxPages parameter is not compensated by the description.

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 compares one-night price distributions (median, quartiles, by type) between Airbnb and Yanolja under the same conditions. It explicitly distinguishes itself from individual listing searches with '개별 숙소가 아니라', which differentiates it from sibling tool search_stays.

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 states when to use the tool: when asking 'which platform is cheaper' or 'what is the market rate in this area'. It also gives a clear exclusion by noting it is not for individual listings, which helps avoid misuse. However, it does not name specific sibling tools as alternatives, so it stops short of a 5.

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