Create a new Illustrator document

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

Given no annotations, the description carries the burden. It discloses that the tool creates a new document and makes it the active document, which implies it changes application state. It does not mention potential side effects like overwriting, but creation tools are typically non-destructive. It also does not disclose whether it returns anything, but that is not critical. The description is honest about the core 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?

The description is a single sentence that front-loads the core purpose and includes essential unit information. No redundancy; each part contributes (new, blank, size, active). Efficient and clear.

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?

For a simple creation tool, the description covers the essential behavior: creation, units for size, and active status. It doesn't mention return values or error handling, but the schema and typical tool behavior suffice. It could mention that it creates a document in the current project or workspace, but given the simplicity, it's fairly complete. The sibling context makes it clear this is the 'new document' 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?

The schema already documents each parameter, so baseline is 3. The description adds the conversion 72pt = 1in, which is valuable for agents understanding units. It also ties width/height to artboard size, reinforcing the schema. The colorMode and name are adequately described in schema, but the unit clarification adds meaning beyond the schema.

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's purpose: 'Creates a new, blank Illustrator document' with specific actions (create, make active). It specifies the resource (Illustrator document) and differentiates from siblings like open_document (which opens existing) and save_document (which saves). The mention of

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 implies usage: it is for creating a new document rather than opening or modifying existing ones. It explicitly states that the document becomes the active document, which guides subsequent tool calls. It does not explicitly exclude alternatives, but the specificity of 'new, blank' makes the use case clear. No prerequisites or caveats are mentioned.

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