TWSE MCP Server

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

No annotations are provided, so the description carries the full burden. It indicates this is a read operation ('get', 'retrieves'), which implies non-destructive behavior, but doesn't disclose other traits like rate limits, authentication needs, or error handling. The description adds value by specifying the scope (yearly, by type and period) and return format, but lacks comprehensive behavioral details for a tool with no annotations.

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 front-loaded with the core purpose in the first sentence, followed by elaboration and return details. It's efficiently structured with three sentences, but the second sentence slightly repeats the first, and the return section could be more concise. Overall, it's well-sized with minimal waste.

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 the tool has 0 parameters, no annotations, and an output schema (implied by 'Has output schema: true'), the description is reasonably complete. It clearly states the purpose, scope, and return format. However, it lacks usage guidelines and could better address behavioral aspects like data freshness or limitations, keeping it from a perfect score.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate. A baseline of 4 is applied as it correctly avoids redundancy, though a 5 would require explicit confirmation of no parameters, which isn't provided.

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's purpose: 'Get yearly issuance volume statistics for listed call/put warrants' and 'Retrieves annual statistics on warrant issuance volumes by type and period.' This specifies the verb ('get', 'retrieves'), resource ('yearly issuance volume statistics'), and scope ('listed call/put warrants', 'annual'). However, it doesn't explicitly differentiate from sibling tools like 'get_warrant_basic_info' or 'get_warrant_daily_trading', which focus on different aspects of warrants.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or compare it to sibling tools such as 'get_warrant_basic_info' or 'get_warrant_daily_trading'. The agent must infer usage based on the purpose alone, which is insufficient for optimal tool selection.

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