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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds value by naming the returned fields (code, price, daily change, volume) and noting paging, but says nothing about ordering guarantees, freshness, or what happens past the last page.

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 sentences, front-loaded with the resource and scope, then the return fields. No redundancy; the only weak spot is the trailing paging clause that adds little.

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?

There is no output schema, and the description does partially compensate by enumerating the returned columns. However, for a ranked/paged list tool it omits direction of ranking, total-count behavior, and any freshness note, leaving gaps an agent might care about.

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 100%, so page, limit, and market are already documented with defaults and max. The description adds only a loose mention of 'ranking offset for paging,' which is slightly inconsistent with the 1-based 'page' parameter, so baseline 3 is appropriate.

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?

States a specific verb-and-resource combination: ranked list of largest listed companies on KOSPI or KOSDAQ by market cap, plus the fields returned. It is clear what the tool produces, but it never mentions how it differs from siblings like kr_search_stocks or kr_quote.

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 guidance on when to use this instead of kr_search_stocks, kr_quote, or kr_index. The market parameter is effectively self-documenting, but there is no explicit when/when-not or alternative routing.

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