Look Up SkyBlock Item

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It details that the tool returns candidate IDs for ambiguous inputs, includes Bazaar or lowest-BIN pricing conditionally, and offers optional wiki context. It does not mention potential side effects or authentication needs, but it adequately discloses core behaviors.

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 a single paragraph that efficiently conveys the tool's purpose, behavior, and key parameter effects. It is front-loaded with the main action and output summary, then details specifics. While not broken into sections, it is dense but clear, with no redundant sentences.

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 7 parameters, no output schema, and no annotations, the description provides enough context for an AI agent to understand the tool's capabilities and return value structure (metadata fields and live value). It misses a formal return schema but compensates with a clear summary of output contents.

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?

The input schema has 100% coverage, so each parameter already has a description. The tool description adds value by explaining how parameters interact (e.g., priceBasis only used for lowest-BIN fallback), the behavior of ambiguous searches, and optional features like includeBazaarOrders and includeWiki. This enhances understanding beyond the schema alone.

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 specifies a clear verb ('Look up'), resource ('SkyBlock item'), and scope ('single item by ID or name'). It distinguishes the tool from siblings by detailing its specific output (metadata, live value) and handling of ambiguous searches, making its purpose unambiguous.

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 provides context for when the tool is appropriate (looking up item metadata and market values) and explains behavior for ambiguous searches (returning candidate IDs). It does not explicitly state when not to use it, but the context signals and sibling names imply alternatives for other tasks.

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