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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are fully covered by structured data. The description adds one genuinely new behavioral fact: prices are denominated in Bazaar Credits. With an output schema present, nothing else is required.

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?

Three terse clauses with the browsing scope and the sibling routing front-loaded; no filler prose. Points off for leading with a bare repetition of the tool name and for an example call ('bazaar_shop_browse {}') that conveys only that no arguments are needed.

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 zero-required-argument, read-only catalog browse with rich annotations and an output schema, the essentials are covered: what is listed, what currency, and which sibling it is not. Only the arena_shop_browse / bazaar_shop_buy adjacency is left for the agent to infer.

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?

Only one optional parameter (key), and the schema documents it at 100% coverage including the Authorization: Bearer alternative, so the schema does the heavy lifting. The description adds no parameter meaning, which meets the baseline-3 expectation for high coverage.

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 concrete verb and resource ('browse cosmetics priced in Bazaar Credits') with illustrative item types (title cards, frames, flair), and explicitly distinguishes it from bazaar_browse_listings (player listings). It loses a point because it never distinguishes itself from the near-identical arena_shop_browse sibling, and the leading repetition of the tool name adds nothing.

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 'WHEN:' clause states the condition for use and directly names the alternative (bazaar_browse_listings) with the criterion that separates them, which is exactly the routing information an agent needs. It omits the natural when-not relationship with bazaar_shop_buy (the purchase counterpart of browsing) and the arena_shop_browse overlap.

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