remotion_generate_video

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's actions (generates files, updates project) and post-execution steps (npm install/start), which is helpful. However, it lacks details on potential side effects (e.g., overwriting existing files), error conditions, permissions needed, or performance characteristics (e.g., time/complexity). The description doesn't contradict annotations (none exist).

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 well-structured and appropriately sized. It front-loads the core purpose, explains the generation process, provides actionable next steps, and includes a concise example. Each sentence adds value without redundancy. Minor room for improvement in tightening phrasing (e.g., 'complete video composition' could be slightly redundant).

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's complexity (generating multiple files and updating project structure), no annotations, and no output schema, the description is moderately complete. It covers the what and how-to-next, but lacks details on output format (beyond 'JSON with generation results'), error handling, dependencies, or integration with sibling tools. For a zero-param tool with significant behavioral impact, more context would be beneficial.

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?

The tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, so it appropriately focuses on behavior and outcomes. No parameter information is missing or needed, justifying a baseline score of 4 for this context.

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: 'Generate the complete video composition and write all files' and 'Generates all TSX components, the composition file, and updates the project with the complete video structure.' This specifies the verb (generate/write) and resource (video composition/files/TSX components/composition file/project structure). However, it doesn't explicitly differentiate from siblings like 'remotion_create_project' or 'remotion_add_title_scene' beyond the scope of generating a 'complete' video.

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 context for when to use this tool: after project creation and before previewing ('After this, you can run 'npm install' and 'npm start'...'). It implies this is a final step in video generation, but doesn't explicitly state when NOT to use it (e.g., vs. incremental tools like 'remotion_add_title_scene') or name alternatives among siblings.

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