get_nuri_contract_data

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

No annotations provided. The description discloses that date-based queries typically allow only 1-month ranges and need splitting, and that fetch_all collects all pages. However, it doesn't cover rate limits, authentication, or error handling.

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 fairly long but well-structured and front-loaded with the main usage pattern. It could be slightly more concise, but every sentence contributes value.

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 covers the 5 parameters thoroughly and provides usage context including a companion tool for exact parameter details. However, it lacks information about the response format, though this is partially mitigated by the companion tool.

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 the description adds meaningful context: explains the operation parameter with examples, lists common fields for params, and warns about date range limitations. This goes beyond the schema descriptions.

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 the tool is for querying the Korean Public Procurement Service OpenAPI for private contract data from the Nuri marketplace. It lists four specific operations, distinguishing it from sibling tools like get_bid_data and get_contract_data.

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 provides explicit instructions: specify an operation, pass query conditions in params, and notes that numOfRows/pageNo/type/serviceKey are auto-handled. It suggests using get_g2b_operation_info for exact parameters and lists common query fields with a date range warning. However, it doesn't explicitly state when not to use this tool.

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