TWSE MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format and data fields well, but fails to mention critical operational aspects such as whether this is a read-only operation, any rate limits, authentication requirements, data freshness guarantees, or potential errors. For a real-time data tool, these omissions are significant.

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 efficiently structured with a clear purpose statement followed by a bulleted list of return fields. Every sentence adds value, though the second sentence could be slightly more concise by integrating the bullet list introduction more smoothly.

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's moderate complexity (real-time data retrieval with detailed metrics), no annotations, and no output schema, the description does a reasonable job explaining what data is returned. However, it lacks important context about operational behavior, data sources, update frequency, and error conditions that would be needed for robust agent 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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on output semantics instead, detailing the structure and meaning of returned statistics. This exceeds the baseline expectation for a parameterless tool.

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 with specific verbs ('obtain', 'returns') and resources ('real-time 5-second trading statistics'), including detailed metrics like order volumes and transaction counts. It effectively distinguishes itself from sibling tools by focusing on high-frequency interval data rather than daily, monthly, or company-specific information found in other 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?

The description provides no explicit guidance on when to use this tool versus alternatives. While the focus on 'real-time 5-second' data implies it's for current market snapshots, there's no mention of specific use cases, prerequisites, or comparisons to sibling tools like get_daily_market_trading_info or get_stock_daily_trading that might offer overlapping functionality.

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