marketplace_backoffice_delete_offer

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the valuable 'Internal API; disabled by default' context, but omits what actually happens on deletion and whether the mode parameter provides a dry-run, which matters a great deal for an irreversible operation.

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, front-loaded with the action and resource. Nothing is wasted, though the second sentence is terse enough to be cryptic rather than merely concise.

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, non-idempotent tool with no output schema and zero parameter documentation, the description should explain the mode semantics, the confirmation field, and the disabled-by-default implications. It gives a single precondition and leaves the operational mechanics unexplained.

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 description coverage is 0% for three parameters, so the description carries the full burden and provides nothing. In particular the 'mode' enum (plan vs apply) strongly suggests a preview/commit pattern and 'confirmation' suggests a safety gate, yet neither is explained anywhere.

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 and resource ('Delete an internal Marketplace special offer'), which is distinguishable from siblings like upsert_offer, list_offers, and delete_application. It does not explicitly name the contrasting sibling, but the resource qualifier 'internal special offer' pins it down well.

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 notes the tool is an 'Internal API; disabled by default', which is a real usage precondition, but it never says when to use this deletion versus upsert_offer or delete_application, nor does it explain the plan/apply modes that presumably govern whether anything is actually deleted.

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