ps_addTextLayer

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

Annotations already declare this is a non-read-only, non-destructive, local operation, so the safety profile is covered. The description adds useful unit details but does not explain whether the new layer is selected, how it is named, or what happens if the font is unavailable.

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 definition is front-loaded with the purpose and then enumerates the configurable fields in one compact sentence. There is no filler or repetition.

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 13-parameter Photoshop tool with almost no schema descriptions, it covers the important creation parameters and units. Minor gaps around color format and optional layer naming keep it from being fully complete, but the core invocation path is clear.

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 8%, so the description must compensate, and it does for most key parameters: font as PostScript name, size in pt, position [x,y] in px, paragraph box [w,h], and styling flags. It still leaves color string format and tracking/leading units unspecified.

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 states a specific verb and resource: adding a text layer in Photoshop. The Photoshop prefix clearly distinguishes it from sibling text-layer tools in After Effects and Illustrator, and the parameter list reinforces the scope.

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?

It gives no explicit when-to-use or when-not guidance. There is no mention of alternatives such as ps_layerOps or how it relates to sibling text tools beyond the Photoshop prefix.

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