delete_channel

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

No annotations are present, so the description carries the full burden. It only says 'Delete', implying a destructive operation, but does not disclose consequences like irreversibility, dependent data removal, permissions, or failure scenarios. This is a significant gap for a mutation tool.

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 a single, focused sentence that states exactly what the tool does. It is concise, has no fluff, and the message is immediately clear, earning a high score for efficiency.

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 simple one-parameter delete, the description is too sparse. It lacks information about return values, side effects, or when to use the tool, and with no output schema or annotations, the burden falls entirely on the description. The tool is not adequately contextualized.

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 input schema already provides 100% coverage with 'id' described as 'Channel ID to delete'. The tool description adds no extra meaning beyond this, so a baseline score of 3 is appropriate since the schema handles parameter semantics.

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 'Delete a sales channel' clearly states a specific action (delete) and a specific resource (sales channel). It distinguishes this tool from other delete_* tools by naming the resource type, and the name aligns with the description.

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?

No guidance is provided on when to use this tool versus alternatives. With many delete_* siblings, the description does not clarify any prerequisites, conditions, or situations where this tool should be chosen over similar delete operations.

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