Delete playlist

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

The annotation 'destructiveHint' already signals destructive behavior. The description adds valuable context: that media stays in the library and that the deletion requires a two-step confirmation with a token. This goes beyond the annotation and increases transparency for the agent.

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 three short sentences, each adding critical information. It's front-loaded with the core action and provides key behavior details with no unnecessary words. Every sentence earns its place.

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 tool with a two-step process and 2 parameters, the description covers the essential behavior and parameter usage. Since there is no output schema, the description mentions the token return implicitly. The behavior is complete enough for the agent, but could optionally mention the expected response format for the first call.

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%, and the description adds meaning beyond the schema by explaining the two-step process: the first call returns a confirmation token, and the second call with that token performs the deletion. This directly clarifies the purpose of the 'confirm_token' parameter.

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 clearly states the tool deletes a playlist, specifies that the media stays in the library, and describes the two-step confirmation process. This distinguishes it from sibling tools like 'remove_items_from_playlist' and clarifies it does not delete media.

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?

The description explains when to use this tool (to delete a playlist) and notes the two-step process involving a confirmation token. However, it does not explicitly state when not to use it or compare to alternatives, though the sibling list helps the agent infer when to use other tools.

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