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

With no annotations, the description must carry the behavioral burden, and it does disclose the returned data set, including the notable 60-trading-day close history that signals response depth. It says nothing about read-only nature, authentication, rate limits, or error behavior (e.g., invalid code), so disclosure is partial.

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 a scope tag up front and no filler; every clause names a returned data element. Nothing is redundant or buried.

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 one-parameter read tool with no output schema, the description usefully enumerates the return fields, which compensates for the missing output schema. It falls short only on error/edge behavior and on distinguishing itself from the closely named sibling fetch tool.

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 'code' parameter is documented in the schema with an example (2330), so the baseline of 3 applies. The description adds no extra parameter meaning such as accepted formats, market prefixes, or whether the stock must be a themed stock.

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 (題材股) and enumerates the exact fields returned (latest close, change %, volume, theme, 60-day closes), which lets an agent understand the payload before opening the schema. It does not, however, distinguish itself from the sibling stocks__get_theme_stocks, whose name implies an overlapping themed-stock query, and the singular code input is not mentioned in the description.

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 gives no when-to-use guidance, no conditions or exclusions, and never names an alternative such as stocks__get_theme_stocks or stocks__list_stock_themes. The tag ［台股題材與高股息］ hints at a scope but is not an instruction about when to select this tool.

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