Live Cancel

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

With no annotations, the description must carry behavioral disclosure. It usefully states the core constraint that only unstarted clips can be cancelled and points to alternatives for playing clips, but it does not say whether removal is permanent, undoable, or requires specific permissions. It adds some behavioral value but leaves important mutation-safety context unstated.

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?

Two tightly written sentences. The purpose is front-loaded, followed immediately by the critical constraint and fallback behavior. 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 simple cancellation tool with an output schema, the description covers the main purpose and limitation adequately. However, with no annotations and 0% schema description coverage, it should also explain the 'project' parameter and clarify the clips array item format. It is minimally complete but leaves meaningful gaps.

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 0%, so the description must compensate for two undocumented required parameters. It partially clarifies the 'clips' parameter by saying IDs come from live_queue / live_view, but gives no format details and says nothing about the required 'project' parameter. The compensation is incomplete.

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 ('Remove') and resource ('clips that have not started yet'), and explicitly distinguishes its scope from playing clips that must instead be stopped or replaced. It also identifies where valid IDs come from (live_queue / live_view), so an agent can tell it apart from sibling live tools.

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 clear when-to-use criteria ('clips that have not started yet') and an explicit when-not/alternative path ('A playing clip cannot be cancelled: queue {track, stop: true} or a replacement instead'). No inference is required to choose between this and stopping a playing clip.

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