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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits: the data is 盤後 (post-market), covers 上市股票 only, and uses 張 as the unit. However, it omits auth needs, rate limits, and return structure.

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 dense sentence covering the key content categories with no filler. The list format is compact and front-loaded, though slightly listy rather than prose-narrative.

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 and no annotations, the description does reasonably well by enumerating what is returned (balances, changes, rankings, top-20 foreign holdings). For a read-only data tool this is close to complete, with only response format details left implicit.

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 single 'code' parameter and its fallback behavior are already documented in the schema. The description adds no parameter detail beyond that, so the 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?

The description names the specific resource and contents: 融資融券餘額與增減, 全市場融資增減排行, and 外資持股比率前 20. An agent can tell this is margin/short-selling chip data for Taiwan listed stocks, though it does not explicitly differentiate itself from siblings like get_tw_market_quotes or get_stock.

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?

There is no explicit statement of when to use this tool versus alternatives, nor any exclusions. The scope note (上市股票) implies usage, but the agent must infer it from the content list rather than being guided.

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