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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond them: the data reflects the latest session, the list is capped at twenty, and ranking is by share volume rather than turnover or price.

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 tight sentences: the substance (what, ranking, fields) comes first, and the example queries follow. The second sentence is slightly redundant with the first, but nothing is wasted.

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?

With no output schema, the description compensates by enumerating returned fields (open, high, low, close, transaction count). Combined with the session-freshness note and row cap, an agent has enough to call and interpret it, though caching or market-closure behavior is unstated.

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% and the single limit parameter (1-20, default 20) is fully documented in the schema. The description restates the twenty-item cap but adds no new semantics for the parameter, so baseline 3 applies.

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 precise verb+resource with scope: the twenty most heavily traded securities on the Taiwan Stock Exchange, ranked by share volume, plus the fields returned. This is clearly distinguishable from sibling reads like taiwan_stock_quote or taiwan_search_securities, though no sibling is named explicitly.

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 quoted example questions ('what is being traded most in Taiwan', 'most active Taiwanese stocks today') imply the intended use case, so a competent agent can route to it. There is no explicit when-not guidance or mention of alternatives such as taiwan_market_summary.

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