vast_delete_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 of disclosing side effects, permanence, or permission requirements. It only says 'Delete' with no information about irreversibility, cascading effects on associated zones, or error behavior. This is a significant gap 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?

The description is a single, front-loaded sentence with no wasted words. However, it is so minimal that it essentially restates the tool name, offering little additional structure or value beyond brevity.

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 delete operation with no annotations and no output schema, the description is critically incomplete. It does not explain what happens to the channel (immediate deletion vs. soft delete), whether it can be recovered, if there are dependencies, or what the response contains. The tool's complexity and destructive nature demand far more context.

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 has one parameter 'id' with description 'VAST channel ID', providing 100% schema description coverage. The tool description adds no parameter information, but the schema already fully documents the only parameter, so the baseline score of 3 is appropriate.

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 VAST channel' clearly states the action (delete) and the resource (VAST channel), distinguishing it from siblings like vast_delete_channel_zone_assignment and vast_delete_archived_channel. However, it adds no detail beyond the tool name, so it is clear but minimal.

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 such as vast_archive_channel or delete_archived_channel. There is no mention of prerequisites, whether the channel must be active, or exclusion conditions, leaving the agent without direction.

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