search_listings

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action of searching, but does not mention the return format, whether results are paginated, what kind of results come back, or any side effects. The description adds almost nothing beyond the tool name.

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 a single short sentence, '당근마켓에서 중고거래 매물을 검색합니다.' It is concise and front-loaded, with no unnecessary words 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?

With 7 parameters and no output schema, the description is insufficient. It does not explain what the tool returns (e.g., a list of listings), how results are sorted by default, or how to effectively combine filters. The description is too sparse to be complete for a tool of this complexity.

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?

The input schema has 100% coverage for all 7 parameters, each with descriptions in Korean (e.g., 'query' = 검색 키워드, 'sort' = 정렬 기준). Thus the baseline is 3. The description itself adds minimal parameter context (used-goods listings) but does not need to compensate for schema gaps.

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 it searches used goods listings on Karrot (당근마켓). It uses the specific verb '검색' (search) and resource '중고거래 매물' (used-goods listings), which distinguishes it from siblings like get_listing_detail and summarize_search_market.

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 gives no guidance on when to use this tool versus alternatives such as get_listing_detail or summarize_search_market. It simply says 'searches listings' without any exclusions or context about choosing this over other search-related tools.

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