get_industry_data

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

No annotations are provided, so the description carries the full burden. It discloses that numOfRows/pageNo/type/serviceKey are auto-handled, and includes a date range constraint. However, it lacks details on error handling, rate limits, or the full behavior of fetch_all beyond 'collect all pages'.

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 concise (few sentences) and well-structured: service definition, usage instructions, operation list, common parameters, and a warning. Every sentence adds value, though some redundancy exists with the schema.

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 no output schema and 5 parameters, the description covers usage and common constraints but does not explain the response structure or error scenarios. The reference to get_g2b_operation_info partially compensates, but the tool could benefit from more details on what to expect.

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 description coverage is 100% with clear descriptions for each parameter. The tool description adds value by listing common query keys and noting the date range limit, which goes beyond the schema. The mention of get_g2b_operation_info for exact parameters further aids understanding.

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 is a tool for querying industry data ('업종 및 근거법규정보 조회') from the Korea Public Procurement Service's open API. It specifies the single operation and resource, distinguishing itself from sibling tools focused on bids, contracts, etc.

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 via operation and params, and provides common query conditions (e.g., inqryBgnDt, inqryEndDt). It includes a warning about date range limits (1 month). However, it does not explicitly state when not to use this tool or provide alternatives.

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