Create Document

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

Annotations already indicate non-idempotence (idempotentHint=false), and the description reinforces this by stating 'Each call creates a distinct item (not idempotent).' It adds context about requiring an open project, which annotations do not cover, thus providing additional behavioral transparency.

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 four sentences long, each sentence serving a distinct purpose: core action, optional parameters, non-idempotence and referral to write_document, and prerequisite. It is front-loaded with the most important information and contains no redundant phrases.

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 presence of an output schema and annotations, the description covers essential aspects: purpose, parameters, behavior, and prerequisites. It lacks explicit mention of error conditions or edge cases, but overall provides sufficient context for a creating 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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining that parentId is optional and if omitted the item goes to the top level, and that content is initial body. This provides context beyond the schema's own 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 text document or folder in the binder and returns its new id, using specific verbs and resources. It distinguishes itself from sibling tools like write_document and delete_document by specifying creation as its unique purpose.

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 explicitly advises using write_document for subsequent content changes, providing clear guidance on when to use an alternative. It also mentions the prerequisite of an open project, but does not list all situations where this tool should be avoided.

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