photoshop_generative_remove_ai

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the AI engine (Firefly) and that removal is autonomous, but says nothing about whether it requires an active selection/mask, whether it mutates the current layer destructively, permission/network requirements for Firefly, or latency. For a destructive image-editing mutation tool, this is a notable gap.

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?

A single, efficient sentence that is front-loaded with the action and resource. No waste.

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?

With no annotations, an opaque nested 'regions' parameter, zero schema coverage, and sibling tools that overlap in function, the one-line description is not sufficient for an agent to call this accurately. The presence of an output schema slightly reduces the burden on return-value description but does not offset the missing input and behavioral detail.

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 0% and there are 2 parameters, one required and nested (regions as array of integer arrays). The description adds no meaning about the format of 'regions' (coordinates? bounding boxes? polygon points?) or what feather_px controls. It fails to compensate for the complete lack of schema documentation.

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?

States a specific verb (removes) and resource (regions) plus the underlying engine (Adobe Firefly Generative Fill). It is largely distinguishable from siblings like photoshop_content_aware_fill, though it doesn't explicitly contrast with the sibling photoshop_generative_fill_ai or photoshop_smart_remove_distractions.

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?

No guidance on when to use this over alternatives like photoshop_content_aware_fill or photoshop_smart_remove_distractions, which occupy adjacent use cases (removing/distraction removal). Only implied usage from the verb 'removes'.

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