get_nuri_bid_data

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

With no annotations, the description carries the full burden. It discloses that serviceKey, numOfRows, pageNo, type are auto-handled, that fetch_all controls full collection, and that date ranges are limited to 1 month. It lacks explicit statement that the operation is read-only, but that is implied by '조회' (inquiry).

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 well-structured with a clear first sentence defining the service, followed by explicit instructions, a list of operations, common params, and a warning. It is somewhat lengthy but all information is pertinent and organized logically.

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?

Given the complexity (multiple operations, no output schema), the description provides essential context: how to use operations, where to find exact parameters, pagination options, and date range limitations. It directs to get_g2b_operation_info for detailed field info, thus covering its interactivity well.

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 5 parameters have schema descriptions (100% coverage). The description adds value by explaining the role of operation (one of 10 listed), the params dict, the fetch_all behavior, and providing a warning about date range limits. It enhances understanding 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?

The description clearly identifies the tool as a query for 조달청 나라장터 OpenAPI to retrieve private bid announcements (민간입찰공고). It distinguishes itself from siblings by being specifically for bid data (not contracts, plans, etc.) and lists all 10 operations with their 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?

The description explains how to use the tool: specify operation and params, use get_g2b_operation_info for details, and warns that date range queries are limited to 1 month. It does not explicitly say when not to use it versus other tools, but it provides enough context for correct invocation.

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