Create a new Clipkit project

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

The description states that passing an existing project_id 'reset[s] that project to blank,' which is a destructive action, while annotations declare destructiveHint=false. This is a direct contradiction, so the description does not transparently disclose the destructive nature. Annotation Contradiction.

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?

Four short sentences front-load the core purpose, then add defaults and usage guidance. Every sentence earns its place with no wasted words.

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 an output schema exists, the description need not detail return structure; it mentions project_id. It covers the main use case, defaults, and reset edge case. However, the contradiction with destructiveHint slightly undermines overall completeness, but the description itself is contextually sufficient.

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%, so baseline is 3. The description adds value by listing defaults (1920×1080, 10s, 30fps, mp4) and explaining the reset behavior for project_id, which goes beyond the schema's description. It does not explain output_dither, but the schema does comprehensively.

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: 'Create a new, blank Clipkit project with the given dimensions and duration, and return its project_id.' It distinguishes itself from siblings by explicitly noting it should be 'first when starting a new video' and describes reset behavior.

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 provides clear usage context: 'Call this first when starting a new video' and explains when to pass an existing project_id for reset. It does not explicitly name alternative tools or state when not to use, but the guidance is sufficient for a new project.

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