Fetch a Ulsan University website guide page's body text, tables, attachments, and links by menu code from site_menu results.
홈페이지 안내 페이지 본문(표 포함)과 첨부·링크. mcode는 site_menu 결과(예: 'MN243' 기숙사, 'MN194' 통학버스).
| Name | Required | Description | Default |
|---|---|---|---|
| mcode | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite lacking formal annotations, the description discloses behavioral traits about the content returned, such as including tables, attachments, and links. This informs the agent about the richness and complexity of the data it will receive, going beyond mere parameter validation.
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 information is dense, perfectly structured across two sentences, and all components contribute to defining the tool's utility and requirements. There is no unnecessary padding.
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 provides the complete context needed for the input (source and meaning of mcode) and defines the scope of the output (what kinds of content are returned). Given that an output schema exists, this definition is highly complete for a content-fetching tool.
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?
Since the input schema provides no description, the description provides maximal semantic value by defining 'mcode' not just as a string, but as the result of the 'site_menu' and giving real-world examples ('MN243' for Dormitory), which is essential for correct invocation.
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 retrieves the content ('guide page body, including tables, attachments, and links'). It is highly specific and easily distinguishes this content retrieval task from simple site searching or menu listing.
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 usage is governed by the input 'mcode'. The description explicitly tells the agent that this code must come from the 'site_menu' tool, creating a clear prerequisite workflow for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.