batch_create_clips

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

No annotations, so description carries full burden. It discloses auto-loading from session state and output format details. Missing: async_mode behavior, potential destruction, dependency on prior steps.

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?

Very concise, front-loaded with 'STEP 3', uses bullet points for readability. Every sentence is informative without excess.

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?

High-level completeness: explains tool's role in workflow, main usage patterns, and output format. Lacks detail on async_mode and clips array schema, but schema covers those. Adequate for a 7-param tool with good schema.

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 3. Description adds value by highlighting export_selected and clip_numbers shortcuts and session state auto-loading, but doesn't explain all parameters beyond schema.

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?

Clear verb 'Export' and resource 'multiple clips at once as finished vertical shorts'. Distinguishes from sibling 'create_clip' (single clip) and positions as step 3 in workflow.

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 two clear usage patterns (export_selected=true or clip_numbers) and implies sequencing (STEP 3). Could explicitly mention alternatives like 'create_clip' for single clips, but context is sufficient.

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