get_creditor_management

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

No annotations are provided, so the description must fully disclose behavior. It indicates a read operation but does not mention side effects, permissions, rate limits, pagination, or output format. The behavioral transparency is minimal.

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 extremely concise: a single Korean sentence stating the purpose, followed by a clear bulleted list of arguments with format and optionality. No unnecessary words, well-organized, and front-loaded.

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 tool has 3 parameters and no output schema, the description covers the basic purpose and parameter formats. However, it does not describe the return value structure or any error conditions, leaving some gaps. It is adequate but not fully complete for a tool in a complex domain.

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 0%, so the description compensates by explaining each parameter: 'corp_code' is an 8-character DART code, 'bgn_de' and 'end_de' are optional dates with YYYYMMDD format. This adds meaning beyond the schema, but it does not explain the parameters' roles (e.g., date range filtering). The description provides format and optionality, making it minimally helpful.

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 retrieves key information about creditor bank management procedure start from a major affairs report. It uses a specific verb ('조회합니다' meaning retrieves) and resource ('채권은행 관리절차 개시 주요 정보'). The sibling 'get_creditor_management_suspension' exists, so this tool is distinguished as handling initiation, giving clear differentiation.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or refer to sibling tools. For a tool with many siblings, this omission limits usability.

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