Scored across 135 tools
There are three parallel, overlapping surfaces: the photoshop_* family, the ps_* family (ps_get_state, ps_get_layers, ps_save_document, ps_export_frame, ps_execute_script) and the recipe/ps_do operation catalog, all covering the same operations. Recipes heavily overlap atomic tools (photoshop_recipe_gradient_fade vs photoshop_apply_gradient_mask vs photoshop_recipe_sky_blend; photoshop_recipe_remove_distraction vs photoshop_content_aware_fill vs photoshop_generative_remove). An agent faces real misselection risk despite detailed per-tool Do-Not-Use notes.
Within photoshop_ tools the verb_noun snake_case pattern is mostly held, but the presence of a second ps_* namespace (ps_catalog, ps_do, ps_batch, ps_skill, ps_recipe) alongside duplicate photoshop_ equivalents breaks predictability. Recipe tools use a recipe_ infix while sibling tools do not, and some tools drop the verb or use divergent verbs (photoshop_play_action, photoshop_image_stack, photoshop_sky_replacement).
135 tools is an extreme over-scoping for any single server; even with a broad Photoshop domain this far exceeds what an agent can reason about coherently. The parallel ps_*/photoshop_* namespaces and duplicated recipe/atomic layers compound the overload rather than adding distinct capability.
The surface is remarkably complete: documents, layers, selections/masks, text, smart objects, artboards, adjustments, generative AI, batch recipes, data-driven templates, export formats, and history/undo. Lifecycle coverage (create/open/save/close/export) and non-destructive workflows are all present with no obvious dead ends.
