get_taiwan_stock_prices

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

Mentions fallback behavior ('FinMind-to-TWSE'), but doesn't elaborate on implications (e.g., latency, data differences). No annotations to provide safety/read hints.

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?

Single sentence packs essential purpose and unique feature. No wasted words.

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 4 parameters and no param documentation, the description leaves significant gaps (e.g., required parameters, data format). Output schema exists but description doesn't clarify return values or usage.

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 coverage is 0% with no param descriptions. The tool description does not explain any parameter, such as source enum values or date formats. Fails to compensate for missing schema docs.

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?

Description clearly states 'Get Taiwan stock prices', specifying the resource and action. The fallback mechanism adds precise scope. This distinguishes it from sibling analysis tools.

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 tool versus siblings like get_taiwan_stock_official_quote or analysis tools. Lacks context for differentiation.

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