기초금액 조회

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

Adds context beyond annotations: explains that only three bid kinds exist for this tool and that unspecified bidKind results in 3 parallel API requests. Annotations already indicate read-only and open-world, so description complements them well.

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?

Three sentences, front-loaded with the primary action, no redundant information. Every sentence contributes unique value, making it concise and well-structured.

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 description fully covers the tool's behavior for a simple two-parameter tool: explains the effect of bidKind on query count, clarifies data scope, and directs to sibling tools. No output schema exists, but the return values (amounts and rates) are implied.

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?

Adds significant meaning beyond the 100% schema coverage: clarifies that bidKind only covers three categories (no foreign/other), and explains the difference in API request count when specified vs. unspecified. This is valuable operational context not in the schema.

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 it retrieves base amount, evaluation standard amount, and preliminary price range rate by bid notice number. It also distinguishes from siblings by naming get_bid_evaluation and get_bid_eligibility for other 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 says when to use ('when base values for budget estimation are needed') and provides alternative tools for related tasks (get_bid_evaluation, get_bid_eligibility). Also explains behavior for specified vs. unspecified bidKind.

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