업종별 종목 시세 조회

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

With no annotations, the description discloses that only the first page (max 100) is returned and that results are sorted by stock code. However, it does not mention auth requirements, rate limits, or whether the operation is read-only.

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?

A single sentence with essential details front-loaded. It is concise, but could be slightly more structured (e.g., separate lines for parameters).

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 no output schema, the description covers the core function, input source, and pagination. However, it lacks details on the return format (e.g., fields in each stock quote) and does not mention error conditions.

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 100%, so baseline is 3. The description adds value by explaining sector_code is from get_market_index and gives examples (001, 101). The limit parameter is already well-described in 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?

The description clearly states it retrieves quotes for stocks in a specific sector, mentions the API code, sorting order, and pagination, and differentiates from sibling tools like get_market_index.

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?

Explicitly tells when to use (getting sector stock quotes) and notes sector_code comes from get_market_index. Mentions limit of 100 items and sorting, but 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.