wiki_search

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

Discloses it returns up to limit results with title, url, and a text snippet. With no annotations, this description fully conveys the read-only, search behavior and hints at query handling.

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?

Three concise sentences: purpose, output, and usage tip. Front-loaded and every sentence adds value. No fluff.

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?

For a simple search tool with an output schema, the description covers input, output, and usage guidance. It is complete and leaves no major gaps.

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?

References both parameters: 'query' in 'matching a query' and 'limit' in 'Returns up to limit results'. With 0% schema coverage, it adds meaningful context, though could further explain query format.

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?

Clearly states it searches the official GW2 wiki for pages matching a query, and distinguishes from sibling wiki_get_page by indicating this tool is for when you don't know the exact page title.

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 advises to use this tool first when uncertain about the title, and provides guidance to reformulate queries using official terms or singular nouns if results are poor.

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