Search GW1 wikis

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

No annotations are provided, so the description carries the full burden. It adds 'via their public MediaWiki APIs' which indicates public access, but it does not explain response format, pagination, rate limits, or error behavior. For a simple search tool, some behavioral context is missing.

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 a single, front-loaded sentence with no filler. It efficiently states the core action and scope, earning its place 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?

For a search tool with three parameters and no output schema or annotations, the description is minimal but workable. It clarifies the data sources and public API nature, but lacks details about return values and result ordering, which would be needed for a fully self-contained description.

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 description coverage is 0%. The description does not explain 'query' or 'limit'; only the phrase 'or both' loosely maps to the 'source' enum. The schema itself provides defaults and enums, but the description does not compensate for the lack of parameter documentation.

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 uses the specific verb 'Search' and clearly identifies the resources (Guild Wars Wiki, PvXwiki, or both). It distinguishes from sibling tools like gw1_wiki_page or gw1_wiki_recent_changes by focusing on cross-wiki search.

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 implies a search use case but does not explicitly state when to use this tool versus alternatives such as gw1_wiki_page. No exclusions or alternative suggestions are provided, though the purpose is reasonably clear from the title and description.

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