wiki_search

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

No annotations provided, so description carries full burden. It discloses that the tool is for title discovery, expects short queries, and is a precursor to other tools. Does not detail output format or error behavior, but adequately conveys non-destructive, read-only nature.

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 concise (two sentences plus a short postscript), front-loaded with purpose, and every sentence is meaningful with no 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?

No output schema exists; the description explains that the tool returns best results to be opened by other tools. It covers search scope (item/NPC/event), but lacks explicit mention of result format (likely list of titles). Sufficient for agent to use correctly given sibling tools.

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 coverage is 100% (both parameters described). Description adds value by reinforcing the '1-3 words' and 'NOUN' constraints, and warns against natural-language questions. Provides examples, which goes beyond schema baseline of 3.

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 finds wiki page titles when the name is unknown, specifies the verb (search/resource: wiki page title), and differentiates from sibling tools like how_to_obtain, wiki_infobox, wiki_page by advising direct calls if the name is known.

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?

Explicitly states when to use ('when you don't already know it') and when not to ('If you already know the name, skip this'). Provides query format constraints ('1-3 words', 'NOUN', not natural-language questions) and recommends alternatives (prefer how_to_obtain for price queries).

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