delete_sales_channel

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

No annotations are provided, so the description carries the full burden. It says 'delete' but does not disclose whether deletion is permanent or reversible, what permissions or scopes are required, what happens to dependent records, or what an error looks like — all critical for a destructive 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?

A single terse sentence with no wasted words, and the verb plus resource are front-loaded. It is arguably too brief rather than padded, so the structure itself is efficient.

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 single-parameter tool with no annotations and no output schema, the description should at minimum mention irreversibility, required permissions, or failure behavior. None of that is present, leaving the agent under-informed about the consequences of calling it.

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 single parameter is fully documented in the schema (ID of the sales channel to delete) at 100% coverage. The description adds no extra meaning such as ID format or where to obtain the ID, so baseline 3 applies.

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 (delete) and resource (sales channel) plus API version context, so the action is unambiguous. It does not explicitly distinguish itself from siblings like list_sales_channel, create_sales_channel, or update_sales_channel, though the verb makes the intent obvious.

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?

There is no guidance on when to use this versus the other sales_channel tools, no prerequisites stated, and no caveats about when deletion is appropriate. The agent must infer everything from the tool name and schema.

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