get_overseas_listing_decision

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

No annotations provided, and description adds no behavioral context (e.g., read-only, authentication, rate limits, side effects). For a query tool, read-only hint would be helpful but is absent.

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?

Extremely concise: one sentence for purpose, then a bulleted list of arguments. No redundancy, every sentence adds value. Efficient structure for quick parsing.

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 annotations and no output schema, the description adequately covers tool purpose and parameter details. Missing return value description, but the tool is a straightforward query; sibling tools have similar simplicity.

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 has 0% description coverage, so description compensates by listing each parameter with format (e.g., '8자리' for corp_code, 'YYYYMMDD' for dates) and optionality. However, no additional semantics like allowable ranges or dependencies.

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 queries overseas securities market new listing decision information from major matters reports. The verb '조회' (query) and resource specification distinguish it from siblings like get_overseas_listing (actual listing) and get_overseas_delisting_decision (delisting).

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, exclusions, or complementary tools. The description only states the function without contextual usage advice.

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