Fetch Configured SkyBlock Wiki Page

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the provenance behavior: a retired official source that returns explicit availability information by default, and replacement content that is explicitly labeled non-official. That is meaningful disclosure an agent could not infer from the schema or annotations.

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 compact sentences, front-loaded with the core action and returning the highest-value provenance caveat alongside it. Slight redundancy between 'configured' and 'non-official' wording keeps it from a 5.

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?

With no output schema, the description does describe what comes back (revision time, cleaned sections, availability status, non-official labeling), which is the essential return-value burden. It is nearly complete for a read tool whose annotations already declare the safety profile.

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 75% (title, search, includeRaw are documented; maxSectionChars is not), so the schema carries most of the semantic load and the baseline of 3 applies. The description adds nothing about parameters, and notably never connects 'cleaned sections' to maxSectionChars, leaving the one undocumented param unexplained.

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?

States a specific verb+resource (fetch a page from the configured MediaWiki source) and even sketches the return shape (revision time, cleaned sections). It implicitly separates itself from the sibling wiki-search tool by being a page fetch, but never names that sibling explicitly.

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?

There is no statement of when to use this tool versus skyblock_wiki_search or any other sibling, and no exclusions. The only usage-adjacent note (retired official wiki returns availability info; replacement content is labeled non-official) describes content provenance rather than selection guidance.

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