photoshop_open_image

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

No annotations provided, so description must carry full behavioral burden. It states the action clearly and the source (filesystem) and destination (Photoshop). But it doesn't disclose whether this creates a new document, whether it fails on unsupported formats, what permissions are needed, or error behavior.

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?

Single concise sentence that front-loads the action and key context. No wasted words.

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?

Output schema exists, so return value details aren't needed. For a simple file-opening tool with one parameter, the description covers the essential purpose. It could add minor details about supported formats or document creation behavior, but is largely complete for an agent to invoke correctly.

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?

Only one parameter, and the description says 'from the filesystem' which implies file_path is a filesystem path (vs URL or other reference). Schema description coverage is 0% but with only one clear parameter, the description provides adequate semantic framing.

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 (open) and resource (image file from filesystem into Photoshop). Distinguishes itself from siblings like photoshop_list_documents and photoshop_create_layer since it is the only tool that opens files from disk into the application.

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?

Usage is implied by the name and description but no explicit when-to-use vs alternatives guidance. For example, it doesn't clarify relationship to photoshop_list_documents or whether it opens into a new document vs active document. But given the tool's specialized nature among siblings, basic context is clear.

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