list_industries

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

No annotations, description indicates read-like behavior (lists existing data) but doesn't specify ordering, pagination, or side effects. Adequate for a simple list.

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?

Two-sentence purpose plus bulleted args. Front-loaded, no fluff. Could be slightly more structured but very efficient.

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 lack of annotations and presence of output schema, description covers basics but misses behavioral specifics (e.g., results format, default behavior, error conditions). Satisfies minimal completeness.

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 coverage is 0%, description provides examples and explanations for both parameters (market filters like '코스피', contains for partial name match), adding significant value over 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?

Clear verb 'list' and resource 'industries', notes inclusion of company count and use for filter selection. Distinguishes from sibling tools which deal with company meta or notes.

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?

States purpose for filter selection but provides no when-not-to-use or alternatives. Siblings don't offer industry listing, so context is adequate but not explicit.

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