Search SkyBlock Storage

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

With no annotations, the description must fully disclose behavioral traits. While it mentions 'decode and merge' and 'large output' for includeSections, it omits critical details: read-only vs write operations, auth requirements, rate limits, data freshness, or potential performance impact. The agent lacks key information to assess safety and constraints.

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 efficiently communicate purpose and output. Every word contributes meaning; no filler or 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?

Given 17 parameters, no output schema, and no annotations, the description is insufficient. It lacks details on return format, pagination, error handling, and how filters interact. An agent would need to infer or guess many operational aspects.

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 coverage is 76%, so baseline is 3. The description adds context for a few parameters (e.g., case-insensitive search, profile selection) but doesn't detail all 17 parameters. The high-level overview helps but relies heavily on the schema for parameter meaning.

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 title 'Search SkyBlock Storage' and description clearly specify the tool's function: decoding and merging items across multiple storage locations (backpacks, ender chest, vault, etc.) and returning grouped counts. This distinguishes it from siblings like skyblock_inventory which likely focuses on a single inventory view.

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 implies usage for aggregated storage searches but provides no explicit guidance on when to use this tool over alternatives like skyblock_inventory or skyblock_audit. No prerequisites, when-not-to-use, or contextual hints are given.

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