ae_addTextLayer

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds some behavior by noting that boxSize produces paragraph text and that position defaults to comp center, but it does not explain creation side effects, active-comp dependency, return behavior, or timing defaults.

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 compact sentence with the core action and key distinguishing behavior front-loaded. Every clause contributes useful information and there is no filler.

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?

This is a 20-parameter creation tool with only 20% schema description coverage and no output schema. The one-sentence description covers several major visual parameters but leaves too many parameters and operational details unexplained for an agent to use the full tool confidently.

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 only 20%, so the description must compensate. It mentions font, size, color, stroke, tracking, leading, justification, position, and boxSize, which adds useful semantic coverage for many creative parameters, but it omits name, allCaps, fauxBold, fauxItalic, duration, startTime, strokeOverFill, centerAnchor, strokeWidth, and compositionName semantics.

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 gives a specific verb and resource: add a text layer in After Effects, and it clarifies point text versus paragraph text when boxSize is supplied. This is clear enough to distinguish it from styling tools like ae_styleText, but it does not explicitly name or contrast the sibling alternatives.

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?

There is no explicit guidance on when to use this tool versus alternatives such as ae_styleText or ps_addTextLayer. Usage is only implied by the tool's action, and no exclusions, prerequisites, or alternative-selection guidance are provided.

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