구매대상물품 조회

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

Description adds significant behavioral context beyond readOnlyHint and openWorldHint annotations: explains multiple API requests based on bidKind, default for bidNtceOrd, and absence of construction category. 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?

Description is concise (4 sentences) and well-structured: first sentence states purpose, second gives usage context, third mentions sibling tools, fourth provides behavioral details. No redundant information.

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?

Despite no output schema, the description adequately covers tool behavior: parameter roles, defaults, parallel request behavior, and relationship to other tools. All relevant aspects for correct invocation are addressed.

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 100%, but description enriches parameters with practical details: enum meanings (thng=물품, servc=용역, frgcpt=외자), request count implications, example for bidNtceNo, and dependency on get_bid_notice for bidNtceOrd.

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?

Description clearly states the verb '조회한다' (query) and resource '구매대상물품' (bid items), specifies key parameters (입찰공고번호와 공고차수), and distinguishes from siblings by naming alternative tools for related purposes.

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 use ('공고에 포함된 물품 내역이 필요할 때'), provides alternative tools for other needs (get_bid_basis_amount, get_bid_eligibility), and explains conditional behavior for bidKind (single vs parallel requests) and bidNtceOrd (default 000 if unspecified).

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