firestarter_delist

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

Beyond the annotations (destructiveHint=true), the description explains the specific effects: buyers' agents can no longer find/buy it, the share link goes dark, and it takes the product off the market immediately. It also calls out the need for user confirmation due to the destructive nature, adding valuable context.

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: the first states the core action and nature (soft delete), the second details effects and a user-confirmation instruction. No fluff, front-loaded.

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 a single parameter, no output schema, and annotations providing the safety profile, the description provides all necessary context: what it does, what happens, and the confirmation requirement. It is complete for this tool's complexity.

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 schema already defines listing_id with 100% coverage, so the baseline is 3. The description adds the nuance that it must be 'one of your listings,' implying an ownership constraint beyond the schema's generic ID description.

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 clearly states the tool's purpose: 'Remove one of your listings from the network (soft delete).' This is a specific verb+resource combination that distinguishes it from sibling tools like cancel (orders) or update_listing (modify rather than remove).

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 clear usage context: it is for removing your own listings, and it explicitly instructs to always confirm with the user before delisting. It does not explicitly mention alternatives or when not to use, but the boundary (your listings) is clear.

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