get_equity_securities_transfer

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'retrieves info' without disclosing side effects, authentication needs, rate limits, or return format. This is insufficient for a safe invocation.

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 sentence of purpose followed by an Args list. No unnecessary words. Front-loaded with the core action, making it quick to parse.

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 lack of output schema, the description does not explain what the result looks like, nor does it mention pagination, errors, or data freshness. For a retrieval tool, this is an information gap, though the parameter formats are well-covered.

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 bears full responsibility. It adds value by specifying that corp_code is an 8-digit DART company code and that dates are in YYYYMMDD format with optional bgn_de and end_de. This clarifies meaning beyond the bare 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?

Description states it retrieves key information on transfer decisions of equity-related bonds, which clearly distinguishes it from siblings like get_equity_securities or get_equity_securities_acquisition. The verb '조회합니다' (retrieves) and specific resource 'transfer decisions' provide clear purpose, though the Korean phrasing may reduce clarity for an English-centric agent.

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 explicit guidance on when to use this tool versus alternatives. With many sibling tools covering equity-related topics, the absence of usage context or exclusions leaves the agent to infer from the name alone.

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