Fetch SkyBlock Resource

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

No annotations are provided, so the description carries full burden. It only states it fetches public resources and supports filtering, but does not disclose any behavioral traits like pagination, error handling, rate limits, or the fact that parameters like 'ids' and 'tier' are conditional on 'kind'. This lack of transparency could lead to misuse.

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 concise at two sentences, front-loading the primary action and listing resource types. Every sentence contributes, though the second sentence is somewhat vague. It avoids unnecessary fluff.

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 7 parameters, no output schema, and many siblings, the description is insufficient. It omits return format, error cases, caching behavior, and does not adequately differentiate from sibling tools. The high complexity demands more completeness than provided.

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 43% (low), so the description must compensate. It adds a general statement about filtering but does not explain parameters beyond what the schema already provides. For example, the meaning of 'kind' enum values, 'search', 'limit', and 'includeRaw' are not elaborated. The description adds minimal value over the schema.

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 fetches public SkyBlock resources and lists specific types (items, skills, collections, election/mayor, bingo, or news). It uses a specific verb and resource, but does not explicitly distinguish from siblings like skyblock_item or skyblock_bazaar, though the list of categories provides implicit differentiation.

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 mentions 'supports filtering for item and resource searches' but provides no explicit guidance on when to use this tool versus alternatives such as skyblock_auctions or skyblock_bazaar. No when-to-use or when-not-to-use information is included, leaving the agent to infer usage context.

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