Three tools with basic descriptions and minimal parameter documentation. All tools are READ_ONLY and well-intentioned, but descriptions lack LLM-optimization guidance (too brief or generic), parameter descriptions are sparse, and output schemas are not documented. No error handling guidance. Tool names follow verb_noun pattern (positive), but parameter documentation is severely underdeveloped. Baseline: 194 chars for tool descriptions (these average ~60 chars); 72 chars for param annotations (these have ~40 chars). No input validation or recovery guidance visible.
获取 Wiki 首页的主要分类列表。
从 Minecraft Wiki 搜索词条完整内容。
从 Minecraft Wiki 搜索词条简介。
Parameter descriptions are minimal or missing. 'keyword' param in search_wiki_intro/search_wiki_full has only ~40 chars; baseline is 72. No guidance on format, length, or constraints. LLMs cannot infer valid input ranges.
Tool descriptions are too brief (avg ~60 chars vs baseline 194). 'search_wiki_intro' description lacks WHEN to use it (vs search_wiki_full), WHAT it returns, or any recovery guidance if keyword not found. Descriptions do not answer: what does it do, when should I call it, what does it return?
Output schemas are not documented. search_wiki_intro and search_wiki_full return str (Markdown), but LLMs do not know the structure, length, or fields. get_wiki_categories returns list[dict] with 'name' and 'description' fields, but this is only visible in the docstring, not in a formal schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If a keyword is not found, tools return 'No intro for X' or 'No content for X', but LLMs are not told what to do next (retry with different keyword, call get_wiki_categories first, etc.). No actionable error messages.
Tool naming does not distinguish search_wiki_intro from search_wiki_full clearly enough. Both start with 'search_wiki_' and differ only in 'intro' vs 'full'. LLMs may conflate them. Consider 'search_wiki_summary' or 'get_wiki_intro' to make the distinction obvious.