Create Document

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

Annotations already specify openWorldHint=false and destructiveHint=false, covering safety. The description adds operational detail: it runs in default background mode and never invokes Computer Use, which is useful context about execution environment. However, it doesn't disclose whether the new document becomes active or how defaults are applied.

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 two concise sentences with no wasted words, front-loading the core purpose.

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 the simplicity of a 3-parameter creation tool with full schema coverage and annotations, the description is adequate but could mention what happens on success (e.g., returns document reference) or interaction with existing documents. No output schema exists, so return behavior is unknown.

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 parameters width, height, and color_mode are fully documented in the schema. The description adds no additional parameter information, so the baseline of 3 is appropriate.

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 clear verb+resource: 'Create a new Illustrator document.' This distinguishes it from sibling creation tools like create_rectangle or create_text_frame. It does not explicitly differentiate from open_document, but the resource 'document' is specific.

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?

There is no guidance on when to use this tool versus siblings like open_document or set_workflow. The description only states what it does, not the context for use.

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