Fetch SkyBlock Resource

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that these are public resources spanning several kinds, but says nothing about rate limits, caching, or the shape/size of results for a multi-kind fetch.

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 tight sentences, front-loaded with the verb and resource, no filler. Brevity is achieved without padding, though it is arguably too terse for a 7-parameter tool.

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 7 params, 43% schema coverage, no output schema, and six distinct resource kinds behind one enum, the description leaves too much unexplained: how filtering interacts with kind, what each kind returns, and the role of includeRaw. It is under-specified for the tool's complexity.

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 only 43% and there are 7 parameters. The description gestures at filtering but never explains search, limit, includeRaw, or which filters apply to which kind beyond the hardcoded schema notes, so it does not compensate for the coverage gap.

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 (fetch) and resource (public SkyBlock resources), and enumerates the supported kinds: items, skills, collections, election, bingo, news. It does not, however, distinguish itself from siblings like skyblock_item or skyblock_bingo that appear to overlap on the same resources.

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 only usage-adjacent sentence is 'Supports filtering for item and resource searches,' which describes a capability rather than when to choose this tool. With siblings such as skyblock_item, skyblock_bingo, and skyblock_wiki_search present, no routing guidance is offered.

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