Create Document

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool launches Illustrator if not running, which is a behavioral trait not in annotations. It also describes return values, providing useful operational context beyond the structured fields.

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 with the core purpose, followed by a behavioral note (launching) and a parameter list. It is reasonably concise, but the parameter list could be condensed without losing clarity. Still, it earns its space without verbosity.

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 tool's complexity (5 parameters, 2 required, no output schema), the description covers all necessary aspects: parameters with defaults, return value, and the behavioral detail of launching Illustrator. It is complete enough for an agent to understand and invoke 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?

Input schema has 100% coverage, so schema already describes parameters. The description organizes them helpfully and adds a note distinguishing color mode usage ('RGB for screen, CMYK for print'). More importantly, it describes the return value (name, size in points, color mode), which adds meaning beyond the input schema and compensates for missing output 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 'Create a new Illustrator document', which is a specific verb+resource. It distinguishes from sibling creation tools like illustrator_create_ellipse or illustrator_create_rectangle, and also mentions launching Illustrator if needed, adding clarity.

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 when to use (when a new blank document is needed) but does not explicitly mention when not to use or provide alternatives like illustrator_open_document. For a simple creation tool, context is clear but excludes guidance.

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