Delete Channel Episode

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, but the description goes beyond them by naming the required permission scopes, describing delegated-token authorization, requiring confirm=true, and warning that the action may share access, notify people, or incur provider charges. That is meaningful side-effect disclosure beyond the structured hints.

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 purpose sentence is front-loaded correctly, but the permission block is heavy per-tool boilerplate that bloats the definition. Content earns its place for auth reasoning, yet the density is higher than an efficient definition needs.

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?

With annotation safety profile, full schema coverage, and no output schema, the description supplies the remaining needed context: auth requirements, confirm gating, and side-effect risk. An agent has enough to call it correctly, though alternatives/routing are absent.

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 100%, so account, confirm and channel_episode_hashed_id are already documented in the schema; the description only reinforces the confirm=true requirement. Baseline 3 is appropriate since the schema does the heavy lifting.

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 (deletes) and resource (channel episode in a channel) in the opening sentence, so an agent can identify the operation immediately. It does not name or contrast with sibling operations like delete_media, delete_channel, or delete_localization, so it stops short of full sibling differentiation.

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?

Provides invocation prerequisites (permission scope, delegated-token behavior, confirm=true) but no guidance on when to choose this tool over alternatives such as delete_channel or delete_media. Usage is implied by the destructive nature rather than explicitly framed as when/when-not.

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