update_wiki

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

Description explains upsert behavior (create if not exists, update if exists). No annotations provided, but the description conveys key behavioral traits clearly.

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?

Very concise: two lines for purpose, then structured argument list. No wasted words, front-loaded with main action.

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?

Covers all 5 parameters meaningfully. Missing return information but no output schema exists. Adequate for typical usage.

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?

0% schema description coverage, but description adds meaningful explanations for each parameter, e.g., 'text: 본문 (Textile 또는 Markdown)' and 'parent_title: 상위 페이지 제목 (계층 구조)'. Adds value beyond schema titles.

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?

Description clearly states 'create/update wiki page (create if not exists, update if exists)' with specific verb and resource. Distinguishes from siblings like 'get_wiki' and 'list_wiki_pages'.

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 explicit guidance on when to use vs alternatives, but the purpose is self-explanatory given siblings. Adequate but lacks explicit context.

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