batch_create_clips

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

With no annotations, the description discloses that the tool auto-loads from session state, outputs H.264 MP4 with specific processing (crop, captions, audio). However, it does not mention permissions, destructive side effects, or failure modes. Some behavioral traits are implied but not fully transparent.

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 concise at ~150 words, structured with a bolded lead, bullet points, and logical order. Every sentence serves a purpose: clarifying usage, defaults, or output. No redundancy or filler.

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 8 params and no output schema, the description covers key aspects: auto-loading, parameter selection, output spec, and async mode polling. It falls slightly short by not describing the synchronous return value or error handling, but is largely complete for practical use.

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 param descriptions. The description adds value by explaining inter-parameter relationships (priority, mutual exclusivity) and typical usage patterns. This goes beyond what the schema provides, justifying above baseline.

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 exports multiple clips as finished vertical shorts, with the action 'export' and resource 'clips'. It distinguishes itself from siblings like create_clip (single) and export_to_davinci_resolve (different format) by specifying batch creation and output format.

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?

Provides explicit guidance on parameter selection: 'Pass exactly one of clips, clip_numbers, or export_selected' and explains priority order. Also gives an 'EASIEST' method and alternative. Though it doesn't reference sibling tools for when-not-to-use, the advice is clear and actionable.

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