Un-publish Channel Episode

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so safety is partly covered. The description adds genuinely useful context beyond annotations: required permission scopes, delegation-token behavior, the confirm=true gate, and side effects (may share access, notify people, incur charges).

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?

Purpose is front-loaded in the first sentence and the requirements follow in logical order. The permission boilerplate is lengthy but information-dense rather than redundant.

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 mutation with no output schema, the description covers auth scopes, the confirm gate, and side effects adequately. Only the when-to-use distinction against sibling episode operations is missing.

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 the schema already documents account, confirm and channel_episode_hashed_id. The description adds no additional parameter meaning (e.g., format of the hashed id or account selection nuance) beyond what the schema provides, so the 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+resource ('Un-publishes an existing channel episode'), clearly distinct from create/publish/delete siblings in action. It doesn't explicitly contrast with publish_channel_episode or delete_channel_episode, 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?

No guidance on when to un-publish versus deleting the episode or updating it; the agent must infer intent from the name. The only operational condition given is the confirm=true requirement, which is a prerequisite rather than a use-case discriminator.

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