create_document

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

Annotations are absent, so the description must convey behavioral traits. It only states the action without disclosing side effects (e.g., whether it opens a new window, overwrites existing documents, requires authentication, or returns a handle). This is a significant gap for a creation tool.

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 extremely short (4 words), but this brevity leads to under-specification rather than efficient conciseness. Key details about usage and behavior are omitted, making it less helpful than a slightly longer, more informative description.

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 13 optional parameters and no output schema, the description should provide more context (e.g., what happens after creation, default behavior with no arguments). It fails to explain the tool's role in the workflow, leaving the agent uncertain about its effects.

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 high (92%), and parameters have decent documentation (dimensions, defaults). The description adds no additional meaning beyond the schema, so 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 'Create a new document' clearly identifies the verb and resource, but it lacks specificity to differentiate from sibling tools like 'create_book' or 'open_document'. It doesn't indicate the document type (e.g., InDesign document from scratch vs. template), limiting its distinctiveness.

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?

No guidance is provided on when to use this tool versus alternatives. For a creation tool with many sibling operations (e.g., 'open_document', 'place_file_on_page'), explicit context is missing, such as prerequisites or typical workflow placement.

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