import_image_sequence

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

The description accurately indicates a non-destructive write operation, consistent with annotations (readOnlyHint=false). However, it doesn't disclose additional behavioral traits like required file naming conventions, handling of missing frames, or where the clip appears after import.

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 a single sentence of 10 words, perfectly concise and front-loaded with the key information. 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?

For a simple two-parameter tool with no output schema, the description gives the essential purpose. However, it lacks details about import behavior (e.g., supported formats, file pattern) and the resulting clip's location, which would be helpful for an AI agent.

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%, meaning the schema already documents both parameters. The description adds no extra meaning beyond the schema definitions, so a baseline score of 3 is appropriate.

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 verb 'Import' and resource 'numbered image sequence', and specifies the outcome 'as a single video clip'. This distinguishes it from siblings like import_media or import_folder, which are more general.

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 implies when to use (when you have a numbered image sequence) but provides no explicit guidance on when not to use or alternatives. The sibling list includes import_media and import_sequences, but no differentiation is made.

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