get_shareholder_info

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

No annotations provided, so description bears full burden. It discloses that the tool retrieves shareholder data but does not detail behavior like authentication, rate limits, or error handling. The default year behavior is noted but overall 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?

Extremely concise: two-line description plus parameter details. No redundancies. Main purpose is front-loaded. Every sentence adds value.

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?

Output schema exists, so return values need not be explained. The description covers both parameters adequately, given the tool's simplicity. However, it does not mention that company_name accepts both name and code, which is a slight omission.

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, but the description adds meaningful semantics: company_name can be name or 6-digit code, year is 4-digit with default previous year. This exceeds what the schema provides (only type and default).

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 the tool retrieves the largest shareholder and holders of 5% or more (주주 현황 조회). The verb '조회한다' (retrieves) and resource '기업의 최대주주 및 5% 이상 대량보유자 현황' are specific. Among siblings like analyze_company_risk or get_financial_summary, this tool uniquely addresses shareholder information.

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 when-to-use or when-not-to-use guidance. The description implies usage for querying shareholder info but does not mention alternatives or context where other sibling tools (e.g., track_insider_trading) would be more appropriate.

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