ps_applyFilter

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds useful context that smart objects should use ps_actionManager for smart filters, but it does not explain that applying a filter alters pixel data or what happens if no layer/document is provided beyond the schema 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 purpose is front-loaded, but the single run-on sentence is dense with braces, parentheticals, and an uncertain 'lensFlare?' that reduces readability. It is not bloated, but it is cryptic and would benefit from clearer structure.

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 filter enum values, a nested settings object, and no output schema, the description covers many filters and the smart-object alternative. Yet the enum/description mismatch and uncertain lensFlare mention leave gaps about which filters are truly supported here and how settings should be supplied for the omitted filters.

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?

The schema has only 50% description coverage and the settings object is generic, so the description adds real value by mapping settings keys such as {radius}, {angle, distance}, and {amount, radius, threshold} to specific filters. However, it is inaccurate or incomplete against the enum: it mentions lensFlare? which is not in the enum, omits sharpen/sharpenMore/blur/despeckle, and says to use ps_actionManager for any other filter despite those enum values being valid here.

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: applying a Photoshop filter to a layer. It also distinguishes this tool from the sibling ps_actionManager for smart-object smart filters and third-party filters, so an agent can identify its niche without opening the schema.

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 explicitly says when to use ps_actionManager instead: on smart objects for smart filters, and for any other or third-party filter. That is clear routing guidance with named alternatives.

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