create-text-layer

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

No annotations provided, so description must bear full burden. It discloses auto-direction and alignment behavior, but omits side effects (e.g., error handling for invalid comp, layer naming, or potential overwriting). Lacks discussion of performance or undo impact.

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?

Two sentences: first states core function, second adds key behavioral detail. No redundant information. Efficient and front-loaded.

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 10 parameters and no output schema, description covers core behavior and Arabic support well. Lacks info on return values, error cases (e.g., invalid comp), and layer naming conventions, but adequate for a creation tool of moderate 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 coverage is 100%, so parameters are well-documented. Description adds value by explaining auto-direction defaults and Arabic font recommendations, which are not in schema. Some defaults like position and font size are mentioned, enhancing clarity beyond raw 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?

Description uses specific verb 'Create' and resource 'text layer', adds Arabic/RTL support detail, and distinguishes from sibling creation tools like create-composition. Clearly states it works on After Effects.

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?

Description implies when to use (when creating a text layer, especially with Arabic/RTL), but does not explicitly state when not to use or mention alternatives. It provides direction auto-detection context but lacks exclusion cues.

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