가격 추이 조회

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

With no annotations, the description carries the full burden. It discloses that the tool reads from the DB only, is fast, and requires prior snapshot collection. It also warns that without data, search_stays must be run first. However, it does not specify what happens if no data exists, leaving a minor transparency gap.

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 two sentences, front-loaded with the core function, then examples, then speed and prerequisite. Each sentence adds value without 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?

For a tool with 5 parameters and no output schema, the description covers the essential context: purpose, when to use, and prerequisite. However, it does not describe the exact return shape or behavior when no data exists, so it's slightly incomplete for a no-output-schema tool.

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 60%, and the description adds some context (snapshot-based, region must match search_stays) but does not meaningfully explain the from/to, source, or excludeAds parameters beyond what the schema provides. The description reinforces that region must align with prior searches but adds no new parameter-level detail.

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 reads daily median price trends from previously collected snapshots, using a specific verb and resource. It distinguishes from siblings by emphasizing it uses pre-collected data and is a read-only DB operation, and it provides example queries that clarify its function.

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 call this tool: when users ask about price changes over time. It also gives a clear prerequisite: if no data exists, run search_stays first over multiple days. This provides both positive and negative usage guidance.

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