Listings deaktivieren (Stufe 2)

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly explains the dry_run default (preview only) and the requirement for confirm_bulk with multiple listings, and states that dry_run:false performs the actual change. This provides important safety context beyond the schema.

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 description is two sentences, front-loaded with the primary action, and every clause adds critical information (confirm_bulk for bulk, dry_run default behavior). No filler or redundancy.

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?

The description covers the essential safety aspects (dry_run, confirmations) and the tool's scope (single or multiple listings). Context is complete for a mutation tool of this complexity, though it doesn't mention return format or error conditions, which is partially mitigated by the dry_run status display and the absence of an output schema.

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 description adds meaningful behavior around the parameters by explaining the interaction between dry_run, confirm, and confirm_bulk, which is not fully apparent from the schema alone. Since schema coverage is 75% and the schema already details each parameter, the description's added semantic value qualifies as above baseline.

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 function: setting one or more listings to 'inactive'. It uses a specific verb ('Setzt'), identifies the resource ('Listings'), and differentiates from siblings like etsy_activate_listing by explicitly naming the target status.

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 guidance on how to use the tool safely (dry_run default, confirm_bulk for multiple listings), but it does not explicitly compare it to alternative tools or state when to prefer this over others. The usage context is implied rather than explicitly contrasted with siblings.

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