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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine content context — that results always include the Prize Shelf and $0 starters, mirroring /arena/prizes — but says nothing about pagination behavior, ordering, or how peer listings mix with house catalog entries. Useful but not rich.

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?

Dense and front-loaded — the WHEN clause and the sibling exclusions come first, followed by the differentiating content guarantee and an example. The leading 'bazaar_browse_listings.' restates the name and is dead weight, and the telegraphic style borders on terse, but nothing else is wasted.

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 an output schema present and rich annotations, the description covers what an agent needs to select and call the tool: purpose, when, alternatives, and a content guarantee. The only soft gap is that it never mentions the auth expectation, which relies entirely on the schema's 'key' description.

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 100% and the enum values are already documented, so the schema carries the parameter burden. The description adds only the implicit signal that all parameters are optional (via the empty-braces example) and nothing about limit/pagination semantics or what 'key' auth fallback means in practice.

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+resource (browse the Dead Brands catalog plus peer listings) and quantifies scope (simulated Credits). It explicitly names the two nearest siblings it is not, so an agent can route correctly without opening any schema.

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 gives the trigger condition directly, and the 'Differs from bazaar_my_goods (your inventory) and booth_feed (direct-swap tape)' line supplies explicit alternatives with parenthetical disambiguation. The zero-arg example call further removes ambiguity about invocation.

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