Create Document

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

Annotations already indicate non-idempotent and non-destructive. The description adds useful context: IT requires an open project, optionally sets content/parent, and returns a new id. No contradictions with annotations.

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?

Three sentences, no fluff. Essential information is front-loaded: creation purpose, optionality, idempotency, and required context.

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?

Covers creation basics, return value, and prerequisites. Lacks mention of error conditions or default content behavior, but given no output schema and presence of sibling tools, it is sufficiently complete for a creation 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?

Adds meaning beyond the schema: 'body content' for 'content' parameter, 'parent folder' for 'parentId', and clarifies 'top level' behavior. Schema covers 'title' and 'documentType' descriptions, so description complements schema well.

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 action ('Create a new text document or folder'), the resource (document or folder in the binder), and the return value (new id). It distinguishes from sibling tools by referencing 'write_document' for content changes.

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?

Explicitly mentions that each call creates a distinct item (not idempotent), provides alternative tool 'write_document' for updates, and states a prerequisite ('Requires an open project'). This gives clear when-to-use and when-not-to-use guidance.

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