get_corp_code

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

No annotations provided, so description carries burden. Describes as a resolution/lookup tool, implicitly non-destructive. Adds context about input format and case-insensitivity. No contradictions.

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?

Reasonably concise two-paragraph structure, but second paragraph could be more compact. First sentence clearly states purpose. Some redundancy in explaining it is an 8-digit identifier.

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?

Complete for a simple tool with one parameter and no output schema. Covers input format, behavior, and provides guidance for non-Korean speakers. No missing details for the agent to use it correctly.

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?

With 0% schema coverage, description compensates by explaining the 'query' parameter accepts either a 6-digit stock code or Korean company name, and is partial and case-insensitive. Adds significant meaning 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?

Clearly states it resolves Korean company name or stock code to DART corp_code, specifying the unique identifier's role. Distinguishes from sibling tools like get_disclosure which likely require corp_code as input.

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?

Provides explicit guidance: accepts stock code (exact) or Korean name (partial, case-insensitive). Includes a workflow hint for non-Korean speakers. However, does not explicitly state when not to use or list alternatives.

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