기초금액 조회

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

Discloses that basis amounts exist only for the three categories (goods, construction, service), not for foreign or others. Explains parallel query behavior when bidKind is unspecified. Annotations (readOnlyHint, openWorldHint) are consistent and description adds value beyond them.

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, no wasted words. First sentence states the main purpose immediately. Second gives usage context, third explains constraints and behavior. Efficient 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?

For a simple retrieval tool with 2 parameters (1 required) and no output schema, the description covers purpose, usage context, constraints, and behavioral nuance. Combined with annotations, it provides complete guidance for correct invocation.

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% with existing descriptions, but the tool description adds context: explains enum values (thng=goods, cnstwk=construction, servc=service) and the parallel logic for unspecified bidKind. This provides meaning beyond 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 the action (retrieve basis amount, evaluation standard amount, preliminary price range rate) and the resource (by bid notice number). It distinguishes from siblings by explicitly naming get_bid_evaluation and get_bid_eligibility for related but separate tasks.

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: 'when you need the reference value for estimated price calculation.' Provides clear alternatives for other needs (get_bid_evaluation, get_bid_eligibility) and explains behavior when bidKind is specified or omitted.

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