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 states 'Get basic information' which implies a read-only operation, but doesn't disclose behavioral traits such as whether it requires authentication, rate limits, what 'basic information' includes (e.g., address, contact details), or if it returns structured data. This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's function.

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 complexity (simple read operation), no annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't explain what 'basic information' includes, the return format, or any behavioral context. For a tool with no structured data to rely on, this leaves significant gaps for an AI agent.

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 tool has 0 parameters, and the schema description coverage is 100% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for no parameters. It doesn't compensate for any gaps since there are none.

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 'Get basic information of broker headquarters' clearly states the verb ('Get') and resource ('broker headquarters'), but it's vague about what 'basic information' entails. It distinguishes from siblings like 'get_broker_basic_info' and 'get_broker_branch_info' by specifying 'headquarters', but doesn't clarify how this differs in scope or content from those 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 is provided on when to use this tool versus alternatives. With siblings like 'get_broker_basic_info' and 'get_broker_branch_info', the description doesn't indicate whether this is for headquarters-specific data, when it's preferred over general broker info, or any prerequisites. Usage is implied by the name but not explicitly stated.

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