某一家廠商的歷年得標清單（一案一列、新到舊），附逐年件數與金額。 name 必須是正式全名（先用 find_entity 查）；year 可用西元或民國年篩選單一年度； unit_id 只看某個機關發給它的案；limit 最多 100，需要更多用 page 翻頁。 award_amount 是這家自己拿到的決標金額：複數決標（同案多家得標或分品項）時不是全案總額， 那種列會另附 winners（得標家數）與 case_total（全案總額）。 要看得標率、對手、往來機關等分析用 vendor_report；要看單一案的開標實況用 get_tender。
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| page | No | ||
| year | No | ||
| limit | No | ||
| unit_id | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
在沒有 annotations 的狀況下，描述承擔了完整的行為揭露：包括 limit 上限 100、用 page 翻頁、year 支援西元/民國年、unit_id 過濾。特別解釋 award_amount 在多廠商得標時不是全案總額，並說明 winners 與 case_total 的附帶資訊，行為細節充分。
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?
描述先講核心功能，再依序說明參數、金額欄位語意，最後給替代工具，資訊密度高但每句都有用途。沒有冗言，長度與五個參數的複雜度相稱。
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?
沒有 output schema，但描述已說明回傳的列結構、金額語意、分頁與前置查詢，足以讓 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?
Schema 對參數的說明覆蓋率為 0%，但描述逐一賦予五個參數意義：name 需正式全名、year 的年度格式、unit_id 的機關過濾、limit 的上限與 page 的分頁方式。所有參數都有超出欄位名稱的語意。
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?
描述以「某一家廠商的歷年得標清單」明確指出工具功能，並補充「一案一列、新到舊、附逐年件數與金額」等格式與排序特性。後段更點名 vendor_report 與 get_tender 分別負責分析與單一案件，與 siblings 有清楚區隔。
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?
明確說明使用前置條件：name 必須為正式全名且先用 find_entity 查詢。也明確給出替代工具的使用時機：「要看得標率、對手、往來機關等分析用 vendor_report；要看單一案的開標實況用 get_tender」。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.