create-composition

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

No annotations are provided, so the description must disclose behavior. It only states 'create', lacking details on side effects (e.g., if a composition with the same name exists), required permissions, or impact on existing project state.

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?

A single sentence of 9 words is maximally concise and front-loaded with the action ('Create a new composition'). Every word carries meaning, no redundancy.

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 7 parameters (3 required, nested object) and no output schema, the description is too minimal. It omits what the tool returns (e.g., composition ID), constraints (e.g., name uniqueness), and interaction with After Effects state.

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 the schema fully describes parameters. The description adds no extra meaning beyond 'with specified parameters', warranting the baseline score of 3.

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 creates a new composition in After Effects using specified parameters. It distinguishes from sibling tools like 'add-any-effect' or 'set-effect-keyframe' which operate on effects, not compositions.

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 for creating compositions but provides no explicit guidance on when to use this tool versus alternatives, or any prerequisites like having an open project.

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