PoE2 Wiki Search

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

The description adds valuable behavioral context beyond what annotations provide: it specifies the source (poe2wiki.net), the return format (up to 5 matching articles with titles and snippets), and provides concrete examples of query types. While annotations cover safety and idempotency, the description adds practical usage information that helps the agent understand what to expect from the tool's behavior.

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 well-structured and appropriately sized. It starts with the core purpose, then provides the Args and Returns sections, followed by helpful examples. Every sentence earns its place by adding specific value - no redundant information or unnecessary elaboration.

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?

Given the tool's moderate complexity, rich annotations, and 100% schema coverage, the description is quite complete. It covers purpose, usage context, return format, and provides examples. The main gap is the lack of output schema, but the description compensates well by specifying what gets returned. It could be slightly more complete by mentioning limitations or edge cases.

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?

With 100% schema description coverage, the baseline is 3. The description adds minimal parameter semantics beyond what's in the schema - it provides examples of query types (skill name, mechanic, item, monster) which gives context about appropriate query content, but doesn't add significant syntax or format details beyond the schema's 'Search query for the wiki' description.

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's purpose with specific verb ('Search') and resource ('Path of Exile 2 community wiki'), and distinguishes it from siblings by specifying it searches for 'game mechanics, items, skills, and other information' rather than currency, prices, builds, or specific pages. This makes it immediately clear what this tool does differently from poe2_wiki_page.

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?

The description provides clear context about when to use this tool (searching the wiki for various game elements), but doesn't explicitly state when NOT to use it or name specific alternatives. The examples help illustrate appropriate use cases, but there's no explicit guidance about choosing between this and poe2_wiki_page or other search-related tools.

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