K-Targo Subway MCP Server

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

With no annotations provided, the description carries full burden of behavioral disclosure. It effectively describes key behaviors: the search functionality, the return data structure (station ID, name, line information), and the automatic suffix removal feature. However, it doesn't mention potential limitations like search accuracy, error conditions, or pagination behavior beyond the parameters.

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 perfectly sized with two focused sentences. The first sentence states the core purpose, the second adds important behavioral detail about suffix handling with a clear example. Every element earns its place with zero wasted words.

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?

For a search tool with 3 parameters, 100% schema coverage, but no output schema or annotations, the description provides adequate but not complete context. It covers the main functionality and a key behavioral feature (suffix removal), but doesn't describe the return format in detail or potential error scenarios that would help an agent use it effectively.

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 100%, so the schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema - it mentions the automatic suffix removal which relates to 'stationName' parameter processing, but doesn't provide additional semantic context about parameter interactions or usage patterns.

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 specific action ('검색합니다' - searches), resource ('지하철역 정보' - subway station information), and scope ('역 이름으로' - by station name). It distinguishes itself from sibling tools like 'get_all_subway_timetables' and 'get_subway_timetable' by focusing on station information search rather than timetable retrieval.

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 implies usage context (searching by station name) but doesn't explicitly state when to use this tool versus the sibling timetable tools. It provides some guidance about the automatic suffix removal feature, but lacks explicit 'when-to-use' or 'when-not-to-use' comparisons with alternatives.

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