create-composition

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 merely restates the action ('Create a new composition') without revealing any side effects, required context, default behaviors, 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, boilerplate sentence that is front-loaded and has no waste. While it is brief, it is not overly verbose, and the schema covers parameter details. It could be slightly more informative, but it remains appropriately concise.

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?

The tool has 7 parameters including a nested object, no output schema, and no annotations. The description is far too minimal to be complete; it fails to mention what happens to the existing project, whether an open project is required, what the return/information out is, or any limitations. A richer description is needed.

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 description coverage is 100% for all 7 parameters, so the schema already provides detailed meanings. The description's phrase 'with specified parameters' adds no extra semantic value, but the baseline of 3 applies because the schema does the heavy lifting.

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, with a specific verb ('Create') and resource ('composition'). It distinguishes itself from sibling tools like set-composition-properties (which modifies existing comps) and create-text-layer (which creates layers).

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?

No guidance is given on when to use this tool versus alternatives. It does not mention prerequisites (e.g., an open project), when not to use it, or how it relates to sibling tools like set-composition-properties. The context is implied but not explicit.

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