Get SkyBlock Inventory Sections

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 output is decoded NBT and that filtering exists, but says nothing about how heavy the default payload is or what triggers the "very large output" flags the schema hints at. Adequate but thin beyond the 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?

Two sentences, front-loaded with the verb and resource, zero filler. The section enumeration is long but earns its place by telling the agent what data is available without opening the schema.

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 16 parameters, no required fields, and no output schema, the description is quite short. It never sketches the shape of the returned sections, item structure, or how the large-output opt-ins change the response, which is a real gap for a tool whose whole job is returning a complex payload.

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 81%, so the schema already explains nearly every parameter (uuid, username, sectionPaths, sectionTypes, includeRawNbt, etc.). The description only alludes to "filters" generically and adds no syntax, format, or interaction detail beyond the schema, so the baseline 3 applies.

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 decode) and resource (inventory-like NBT sections for one SkyBlock profile), and enumerates what those sections cover: wardrobe, armor, equipment, ender chest, backpacks, vault, bags. It is clearly distinguishable from decode_skyblock_nbt at a conceptual level, though it never names that sibling or skyblock_storage to draw the boundary 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?

"Use filters to keep output focused" is a mild operational tip but not real when-to-use guidance. Nothing tells the agent when this tool is preferable to skyblock_storage, decode_skyblock_nbt, or skyblock_profile, nor are any prerequisites (e.g. needing a profileId first) stated.

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