photoshop_set_active_document

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

While annotations cover idempotence and non-destructiveness, the description adds important behavior beyond structured fields: preconditions, the exactly-one-selector rule, side effects on the active tab, and a return JSON shape.

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 front-loaded and tightly organized with labeled sections for usage, exclusions, returns, preconditions, and side effects. Every line contributes actionable information.

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?

Given no output schema, the description still documents the return shape. It covers selection constraints, preconditions, and side effects, leaving no significant gap for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds valuable constraints beyond the schema: document_id is preferred, duplicate names make document_name ambiguous, and exactly one selector must be provided.

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: switching the active document tab. It distinguishes the tool from siblings like photoshop_list_documents and photoshop_set_active_artboard by naming the exact target and the accepted selectors.

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?

It gives explicit when-to-use and when-not-to-use guidance, including the single-document case. It also names the correct sibling for resolving duplicate document names and tells the agent to prefer document_id.

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