구매대상물품 조회

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

Description matches readOnlyHint (조회) and explains parallel query behavior for bidKind categories and default value for bidNtceOrd. 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?

Concise, well-structured sentences with main purpose first, then usage guidance, then parameter details. No fluff.

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?

Covers purpose, usage, parameters, and hints at output fields. No output schema, but description mentions typical fields. Lacks details on pagination, limits, or error conditions.

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?

All parameters have schema descriptions (100% coverage). The description adds context beyond schema: explains bidKind values and parallel query, and bidNtceOrd default and source.

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 retrieves bid items (name, quantity, unit price, delivery place) using bid notice number and order. It distinguishes from siblings by naming alternatives for base amount and eligibility.

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 says when to use ('when you need the list of items in a notice') and provides alternative tools for other purposes. Also specifies parameter behavior for bidKind and bidNtceOrd.

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