Un-publish Channel Episode

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

Goes beyond the annotations by disclosing the required permission scopes, the delegated-token behavior, the confirm=true gate, and the warning that the action 'may share access, notify people or incur provider charges.' That is real behavioral context the destructiveHint annotation alone does not convey. Missing is any statement of reversibility or the resulting episode state.

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?

Front-loads the action in one clear sentence before the permission block. The permissions text is somewhat boilerplate and multi-line, but it is relevant and not padded with fluff.

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-entity mutation, the description covers auth, confirmation, and side-effect risk, with the annotations carrying the safety profile. It lacks only what the un-publish does to the episode (draft? URL invalidated?) and whether it can be undone, though no output schema exists to offset that gap.

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 restates the confirm requirement, adding no syntax, format, or edge-case detail beyond the structured fields.

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') that clearly distinguishes it from the sibling publish_channel_episode. It stops short of naming the sibling or describing the resulting state, but the action is unambiguous.

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?

Gives concrete prerequisites (required token permissions and confirm=true), which is useful operating guidance. However it never states when to choose this over publish_channel_episode/update_channel_episode or what condition should trigger an un-publish.

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