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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes further by enumerating the actual side effects: cancelling open listings, clearing the showcase, and marking the wallet deregistered. It also discloses the recovery path (rejoin via claim_daily or create_listing), which is behavior an agent cannot infer from the annotations alone.

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 WHEN/effect/alternative content is front-loaded and dense with no filler. The trailing example ('bazaar_deregister {"target":"<target>"}') adds no information and slightly dilutes an otherwise tight definition.

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 destructive, multi-mode tool whose annotations and schema are rich, the description covers the essential outcomes and the sibling distinction. It is silent on what happens to in-flight offers/proposals when the bot leaves the Bazaar, which matters given the presence of bazaar_check_my_offers and bazaar_resolve_proposal, but that is a minor gap.

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 for target is documented with its meaning, so the schema does nearly all the work. The description restates the target=listing + listing_id conditional but adds no format, syntax, or edge-case detail beyond what the schema already says.

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 names a specific verb+resource (deregister from the Bazaar) and immediately decomposes it into two modes (cancel a single listing vs. leave entirely). It explicitly contrasts itself with the sibling bazaar_cancel_listing, so an agent can pick the right tool without opening schemas.

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?

Opens with an explicit 'WHEN:' clause, then gives the condition for each target mode (owner cancels one listing vs. full exit), and names the alternative shortcut tool. It even supplies the re-entry path via claim_daily or create_listing.

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