photoshop_set_active_document

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

With no annotations provided, the description carries the full behavioral burden and largely succeeds: it discloses side effects ('changes active tab'), preconditions ('target document must be open'), and the exact return shape. It does not discuss error behavior for invalid or missing identifiers, but the core behavioral traits are clearly stated.

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 description is compact and well-structured, with the primary action front-loaded and use conditions, returns, preconditions, and side effects each earning their place. There is no redundant filler.

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?

Despite having no output schema, the description documents the return JSON shape, the precondition that the document must be open, the ambiguity caveat for duplicate names, and the side effect of changing the active tab. This is fully sufficient for an agent to select and invoke the tool 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?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by emphasizing that document_id is preferred, warning against document_name when duplicates exist, and requiring exactly one of the three parameters even though the schema marks none as required.

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: 'Switch the active document tab' by document_id, index, or name. It clearly distinguishes this tool from siblings like photoshop_list_documents and photoshop_get_document_info by focusing on changing the active tab rather than inspecting or creating documents.

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?

Explicit 'Use when' and 'Do NOT use when' conditions are provided, including the case of a single open document and duplicate document names. It also names the recommended source for document_id (photoshop_list_documents), giving clear routing guidance.

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