Fetch Official SkyBlock Wiki Page

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

With no annotations, the description carries full burden. It discloses the return format and section extraction for items, but does not mention error handling, authentication, rate limits, or what happens if a page is not found.

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 sentences with minimal waste. The first sentence introduces the purpose and method, and the second provides a concrete example. Front-loaded and efficient.

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?

Despite clear purpose, the description lacks detail on the exact return format (e.g., JSON structure) and error scenarios. With no output schema, the agent may be uncertain about the expected response.

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 high (all parameters have descriptions). The description adds value by clarifying the interaction between 'title' and 'search' and specifying what sections are extracted for item pages, going beyond the schema definitions.

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 verb 'Fetch', the resource 'one official Hypixel SkyBlock Wiki page', and the return format 'cleaned AI-readable section summaries'. It also provides a specific example for item pages, distinguishing it from the sibling 'skyblock_wiki_search' which is for 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 this tool is for single pages compared to skyblock_wiki_search, but does not explicitly state when to use this versus alternatives. It mentions behavior for item pages but lacks when-not or prerequisite guidance.

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