createComposition

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states 'Create' without mentioning side effects (e.g., adding to the current project), requirements (e.g., After Effects must be running), or return values. This is a significant gap for a mutation tool.

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 concise sentence that is easy to parse and front-loaded. It wastes no words, but it is under-specified for a tool with five parameters and no annotations, making it feel minimal rather than appropriately sized.

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?

Despite full schema coverage, the description lacks critical behavioral context such as what happens after creation, whether it affects the active project, or any prerequisites. With no output schema and no annotations, the description is incomplete for an agent to fully understand the tool's behavior and impact.

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 input schema covers 100% of the parameters with descriptions and defaults, so the schema already provides full parameter semantics. The description adds no additional meaning beyond the tool name, keeping the baseline of 3 because it neither enhances nor detracts from schema information.

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 'Create' and the resource 'After Effects composition', making it distinct from siblings like run-script or importFootage. It is specific enough to identify the tool's primary function, though it lacks explicit sibling differentiation or additional context like whether it creates in the active project.

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 usage: use this tool to create a new After Effects composition. However, it does not explicitly state when to use it versus alternatives or mention any prerequisites. Since the sibling tools are all different operations, the implied context is clear but not fully articulated.

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