search_company

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

With no annotations, the description carries behavioral disclosure. It clarifies that listed_only filters to companies with a stock code and that limit caps results, which adds behavioral context beyond the schema. However, it does not mention read-only status, error behavior, or other operational traits, though 'Search' implies a non-mutating operation.

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 compact and well-structured: a one-sentence summary followed by clearly labeled parameter explanations. There is no redundant content or restating of schema fields beyond what 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?

For a simple search tool with an output schema and three parameters, the description provides enough information to invoke it correctly. It could be more complete by distinguishing itself from get_company_profile_by_query and noting whether the result is a list or a single profile, but the output schema likely covers return shape.

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 fully compensates. It explains the query format with Korean examples, defines listed_only as filtering to stock-code-bearing companies, and specifies the valid range for limit (1–50), which the schema omits. Every parameter receives meaningful, actionable semantics.

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's function: 'Search DART companies by company name, stock code, or corp code.' This is a specific verb and resource with concrete query types. It does not explicitly differentiate from sibling tools like get_company_profile_by_query, but the purpose is unambiguous.

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 implies this tool is used when you need to find DART companies using a name or code, but it does not explicitly state when to prefer it over alternatives such as get_company_profile_by_query or search_disclosures. No when-not-to-use guidance is provided.

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