addTextAnimator

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

With no annotations, the description carries the full behavioral burden and mostly does not. It never says the tool mutates an existing text layer, whether it adds a second animator alongside existing ones, whether the operation is undoable, or what happens if the target layer/composition is missing.

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 front-loaded sentence with the core verb first and details following. The parenthetical preset list duplicates the schema enum, but it is compact and aids selection rather than bloating the text.

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 tool with 10 parameters, nested rangeSelector/wigglySelector objects, and no output schema, the description covers only the preset dimension. It omits how presets interact with custom properties and selector configuration, leaving real gaps for a tool of this complexity.

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% with 10 well-described parameters, so the baseline is 3. The description only restates the preset enum and the "per-character 3D" note for 3d_flip_chars, adding essentially no semantics beyond the schema.

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?

States a specific verb and resource ("Add an AE text animator") and enumerates the two capability modes: full selector/property control or predefined presets. No sibling tool touches text animators, so the agent can place it immediately.

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 phrase "or custom" hints that presets and manual properties are alternative paths, but there is no statement of when to pick one over the other, no prerequisite that a text layer must exist, and no guidance on combining rangeSelector vs wigglySelector. The agent must infer the usage model.

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