clip_unlink_proxy

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

The destructiveHint annotation already indicates the operation is destructive. The description adds context by specifying the resource (proxy media link) and the target (clip), but it does not disclose whether the proxy file itself is deleted or if any other side effects occur. This is adequate with annotation support but not richer.

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 a single, concise sentence (7 words) that is front-loaded and contains no unnecessary words. Every word contributes to conveying the tool's purpose.

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?

This is a simple tool with one parameter, and the schema documents that parameter fully. An output schema exists, so return values need not be explained. The description plus annotations provide enough context for correct usage, though slightly more detail about side effects could elevate it.

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 coverage is 100% and the parameter description ('Name of the clip whose proxy link to remove') is already explicit. The tool description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Remove') and resource ('proxy media link') with a clear object ('from a clip'). It directly explains the tool's function and is easily distinguished from the sibling tool clip_link_proxy, which performs the inverse operation.

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 clearly implies the usage context: when a proxy link needs to be removed from a clip. It doesn't explicitly mention alternatives or exclusions, but the operation is obvious given the sibling tool clip_link_proxy. This meets the 'clear context, no exclusions' level.

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