Set text content and style

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

The description's 'change' matches readOnlyHint=false, so there is no annotation contradiction. But it adds little behavioral context beyond that: it doesn't say what happens if the layer or comp is omitted, whether unspecified style properties are preserved, how invalid fonts or colors are handled, or what the tool returns. With 12 optional parameters, the description leaves the mutation behavior largely undisclosed.

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 tight sentence with no filler and front-loads the main action. It is concise without being bloated, but it sacrifices useful operational detail that other dimensions need; the brevity itself is not a flaw, but the sentence is more of a restatement of the title than a substantive expansion.

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 12 parameters, zero required parameters, no output schema, and only minimal annotations, this description is too thin. It does not mention the optional-layer/comp fallback behavior, the absence of required arguments, parameter categories, or likely failure modes, leaving an agent under-equipped to invoke it correctly on a complex text-layer mutation task.

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 58%, and the description does not compensate for the undocumented parameters. 'String and character styling' is a useful umbrella for text, font, color, leading, tracking, etc., but it does not clarify the ambiguous parameters (tracking, allCaps, strokeWidth, justification, fontSize) beyond what their names already imply.

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 uses a specific action ('change') and a clear resource ('the string and character styling on a text layer'), so an agent can tell it targets text content and typography. It does not explicitly contrast itself with sibling tools like ae_set_layer or ae_set_property, but the scoping to text layers is enough to avoid gross confusion.

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 'on a text layer' implies the intended use: modify a text layer's content and character-level style. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as ae_set_property or ae_set_layer, leaving the decision partly to inference.

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