ae_add_text_reveal

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

With no annotations, the description explains the internal mechanism (Text Animator, Expression Selector) and how parameters affect behavior, but does not disclose whether the tool creates a new text layer or modifies an existing one, nor potential side effects like undo behavior.

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 concise (three sentences), front-loads the key differentiator ('not a flat fade'), and each sentence adds value without 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 13 parameters, no output schema, and no annotations, the description covers the core mechanism well but omits high-level context such as whether it creates a new text layer (likely based on the required 'text' field) and the nature of the 'comp' parameter.

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 62%, and the description adds useful context for parameters like chunkSize, basedOn, offsetY, and perChunkSeconds with examples. However, parameters like comp and startTime lack any additional explanation in either schema or description, leaving gaps.

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 it's a 'word-by-word staggered text reveal' and explicitly contrasts with a 'flat fade,' distinguishing it from sibling tools like ae_add_fade. The mechanism and customization options are well explained.

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 when to use (staggered reveal) versus alternatives (flat fade), but does not explicitly state prerequisites, limitations, or when not to use this tool relative to other text animation tools.

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