Decode SkyBlock NBT

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful context about the input encoding and the two-part output shape, but says nothing about failure behavior on malformed/corrupt Base64-gzip payloads or the input size limit that constrains large payloads.

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?

A single front-loaded sentence with no filler; the decode operation, the input format, and the output shape are all stated without redundancy.

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?

There is no output schema, so the description's brief note about returning plain JSON plus a compact item list is helpful, and annotations carry the safety profile. However, for a 3-parameter transform tool with 0% schema coverage, the definition is not complete enough: parameter behavior and error handling are left entirely unspecified.

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 0% and three parameters (data, maxItems, includeRaw) are undocumented in both schema and description. The mention of 'plain JSON and a compact item list' only loosely gestures at includeRaw and maxItems; it never states that maxItems caps the item list or what includeRaw toggles.

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?

Names a specific verb (decode) applied to a precise resource (a Hypixel SkyBlock base64 gzipped NBT inventory/item payload) and states the produced artifacts (plain JSON and a compact item list). No sibling in the list performs this same transform, so an agent can identify it immediately.

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?

Usage is only implied by the input type ('base64 gzipped NBT payload'), which suggests 'use this when you already hold raw NBT'. There is no explicit when-to-use, no when-not-to-use, and no guidance on how this relates to siblings like skyblock_inventory or skyblock_storage that likely surface similar item data.

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