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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds non-annotation facts: the ~5-second refresh cadence, the MIS source, and that the source 'is not covered by the Open Government Data License', along with the per-quote trading date.

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?

Content is front-loaded (what it returns, refresh cadence, scope) followed by the usage boundary and market mapping. The bilingual presentation duplicates parts of the English text in Chinese, which costs some efficiency, but every block still carries distinct information.

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 read-only quote tool with an output schema present, the description covers source, licensing, refresh cadence, item limits and market semantics. It omits auth requirements and error/empty-result behavior, which would round it out to a 5.

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 the baseline is 3. The description adds semantic value beyond the schema by mapping the enum to real-world asset classes ('ETF 與上市股票用 market="tse"，上櫃用 "otc"') and restating the 50-item cap.

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 ('Intraday quotes'), a precise scope ('up to 50 TWSE-listed (market="tse") or OTC (market="otc") codes'), and the real-time differentiator ('refreshed about every 5 seconds'). It does not name a sibling (e.g. quote.lookup) to contrast against, so sibling differentiation is left implicit.

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 clause 'OpenAPI 只有前一交易日資料，要當下的價格得走基本市況報導站' gives a clear when-to-use condition (needing the current price) versus previous-day data, plus market selection guidance ('ETF 與上市股票用 market="tse"，上櫃用 "otc"'). It stops short of naming an alternative sibling tool or stating exclusions explicitly.

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