twse_get_dataset

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

With no annotations, the description carries full burden. It discloses server-side filtering, a hard limit of 200 for limit parameter, and auto-detection of code column name. However, it omits error handling, permissions, rate limits, or idempotency, so it's adequate but not comprehensive.

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?

The description is concise and well-structured: a one-sentence purpose, a crucial usage warning, then a bullet list of args. Every sentence adds value with no 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?

The description covers core usage, filtering, and pagination. Since an output schema exists, return format is not needed. It lacks error handling or prerequisites, but for a data retrieval tool with good parameter docs, it's nearly complete.

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%, so the description fully compensates. It explains all 6 parameters with concrete examples (e.g., dataset_id like 'exchangeReport/STOCK_DAY_ALL', code like '0050', match as dict, fields as array), adding meaning beyond the schema's type-only definitions.

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 '取得證交所資料集內容' (get TWSE dataset content) with support for server-side filtering, field projection, and pagination. It distinguishes from siblings like twse_search_datasets (search) and twse_describe_dataset (describe structure) by focusing on retrieving actual data rows.

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 second paragraph explicitly advises using code/match/fields to narrow scope and warns against unconditional full pulls ('不要無條件拉全部'). It provides examples for each parameter and implies when to use filtering, fulfilling the when-to-use and when-not-to-use criteria.

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