clip_history

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

The description only mentions viewing and checking, but the schema includes a 'delete' action, which is destructive and not disclosed. Without annotations, the description should cover all key behaviors, but it omits the deletion capability, making it misleading.

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 sentences, concise and front-loaded with the purpose. Every word serves a clear function, with no 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?

Given the tool has 9 parameters and three actions (list, check, delete), the description only covers two actions (view and check). It does not mention the delete functionality or return value format, leaving gaps for a tool with moderate complexity.

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% with parameter descriptions, so the baseline is 3. The tool description adds no additional parameter-level meaning beyond what the schema already provides.

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's purpose: viewing previously created clips and checking for duplicates before creating new ones. It effectively distinguishes from sibling tools like 'create_clip' and 'modify_clip' by focusing on pre-creation verification.

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 explicitly instructs the user to check before creating new clips, providing a direct usage guideline for when to use this tool. It implicitly advises against using it for creation or modification, which is covered by sibling tools.

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