clip_history

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

With no annotations, the description carries the full burden of behavioral disclosure. It presents the tool as a read-oriented 'View'/'Check' action, but the schema reveals a destructive 'delete' mode; the description does not warn about this side effect or disclose any other behavioral traits such as output or filtering behavior.

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 short sentences, no filler, and the key purpose and usage guidance are front-loaded. Every word 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?

This is a multi-mode tool with 9 parameters, no output schema, and no annotations, yet the description only covers the duplicate-checking use case. It fails to mention the list/check/delete action modes or the destructive delete capability, so an agent is not fully equipped to use it safely and completely.

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%, with each parameter already annotated for its applicable action (e.g., 'for delete', 'for check'), so the baseline is 3. The description itself adds no parameter-level meaning beyond that, but it does not need to because the schema is complete.

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 names a specific resource ('previously created clips') and a clear purpose ('avoid duplicates'), which distinguishes it from creation-focused siblings like create_clip and suggest_clips. However, it omits that the tool also supports deletion via the action enum, so the full scope is not stated.

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?

'Check before creating new clips' is an explicit, actionable directive telling the agent when to invoke this tool relative to clip creation. It does not mention alternative tools or when not to use it, but the core usage context is clear.

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