Create Document

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

Annotations already indicate the tool is not read-only and not destructive, so the description's main addition is that it creates a document. It does not disclose side effects, permissions, or what happens if the document name conflicts, but the basic safety profile is covered by annotations.

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 sentences, each containing essential information. The first sentence states the primary action, the second explains key options. No unnecessary 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?

With 8 parameters including nested objects and no output schema, the description covers main use cases but omits important context like return values (e.g., document ID) and error conditions. Some guidance on behavior when presets override dimensions would improve completeness.

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 schema already documents each parameter. The description adds value by grouping parameters into usage patterns: presets vs custom dimensions, and optional background/guides. This contextualizes the parameters beyond individual descriptions.

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 clearly states the tool creates a new Photoshop document, with specific verbs and resource. It distinguishes between using presets for common sizes or custom dimensions, which sets it apart from sibling creation tools like ps_create_layer or ps_create_design.

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 provides guidance on when to use presets versus custom dimensions, which is helpful. However, it does not explicitly exclude cases where this tool should not be used or mention alternatives like ps_create_design for templates.

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