Fetch SkyBlock Bazaar

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that it returns prices, volumes, and spread signals, but says nothing about pagination, rate limits, or refresh freshness, leaving the lower-bar behavioral disclosure only partially met.

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 tight sentences, front-loaded with the core action, with no filler. It earns its place but is quite short given the parameter surface it must support.

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?

For a 6-parameter tool with 0% schema coverage and no output schema, the description omits all parameter semantics and only gestures at the return payload. An agent cannot tell how to constrain or shape results from the description alone.

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% across 6 parameters (limit, search, sortBy, includeRaw, productIds, includeOrders), so the schema does the documentation work but with no descriptions at all. The description compensates by explaining none of the parameters, so an agent gets no guidance on sorting, filtering, or the raw/orders flags.

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 gives a specific verb (Fetch) and resource (Bazaar product prices, volumes, and spread signals), which is clear and concrete. It does not distinguish this from siblings like skyblock_auctions or skyblock_item, so it stops short of a 5.

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?

"Useful for money-making tips and crafting cost checks" implies the use context but gives no explicit when-to-use versus alternatives (e.g., auctions for player listings). Usage is suggested rather than stated.

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