twse_search_datasets

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

No annotations provided, so description must fully disclose behavior. It explains the search behavior, parameter effects, and that it matches codes/descriptions/field names. No destructive or side effects mentioned, but as a read operation this is acceptable. It lacks rate limit or permission info, but not critical.

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?

Description is concise: two sentences plus parameter list. Front-loaded with purpose, each sentence is necessary. No fluff or redundancy.

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?

Given an output schema exists, return values need not be described. The description covers purpose, parameters, and usage context (TWSE OpenAPI). Could mention that results include dataset_id, but output schema handles that.

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 0%, yet the description adds rich meaning: query with examples (ETF, 基金), tag with examples (證券交易, 公司治理), and limit with default 25. This fully compensates for missing schema descriptions and helps agents understand usage.

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 clearly states the tool searches TWSE OpenAPI datasets to find dataset_id before fetching data. It specifies matching against codes, descriptions, and field names. This distinguishes it from sibling tools (describe, get, realtime quote, snapshot) which serve different purposes.

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 advises using this tool before fetching data and provides parameter usage details (e.g., empty query lists all, tag filters by category). It does not explicitly mention when not to use it or alternatives, but the context and sibling names imply search is for discovery.

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