Search Official SkyBlock Wiki

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

No annotations provided, so description carries full burden. It describes the tool as a search via the MediaWiki API, which implies read-only behavior. However, it does not explicitly state it is safe or discuss rate limits or side effects. Adequate but not exhaustive.

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?

Two concise sentences, front-loaded with the main action and use cases. No unnecessary words.

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 has 2 parameters and no output schema, the description covers purpose and general usage but lacks details on the 'limit' parameter and return format (e.g., page titles, snippets). Could be more complete for a search tool.

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 50% (only 'search' has a description). The tool description does not explain the 'limit' parameter or its default/range. With low schema coverage, the description should compensate but does not add any parameter details.

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 searches the Hypixel SkyBlock Wiki via its MediaWiki API, and lists specific use cases (item, mechanic, update, NPC, location, guide-page discovery). It distinguishes from sibling 'skyblock_wiki_page' which likely retrieves a single 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 says 'Use this for... discovery,' implying it's for searching rather than retrieving a specific page, but it does not explicitly state when not to use it or mention alternatives like 'skyblock_wiki_page' for direct page access.

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