adobe_open_copy

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that it creates a copy and requires a new destination, but omits permissions, error behavior if the destination exists, and what 'owned' implies.

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?

Two tight sentences with the purpose and key constraint front-loaded, and no wasted wording. Terms like 'owned' and the 'workspace PSD/AI/PNG/SVG' notation are slightly jargon-heavy but not verbose.

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?

The output schema covers return values and annotations cover safety, so the description need not repeat those. It still leaves meaningful gaps around source/destination semantics and sibling alternatives, which matter for a three-parameter file-creation tool.

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%, so the description must compensate. It hints that source is a workspace file in PSD/AI/PNG/SVG, application corresponds to PSD/AI, and destination must be new, but gives no path syntax, validation rules, or extension expectations.

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 action (open a new owned copy) and resource (PSD/AI copy), including source workspace formats and the destination constraint. It does not differentiate from siblings such as adobe_close_copy or adobe_create_canvas, so it falls short of a 5.

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?

The description gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. The only guidance is the constraint that the destination must be new, leaving the agent to infer that this is for starting a fresh copy rather than editing an existing file.

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