Create new Docling document

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

The description discloses that the document is persisted in the local document cache and that a key is derived from an MD5 hash of the prompt, both useful behavioral details beyond the annotations. The annotations already indicate a non-read-only operation, so this additional context is reasonable and does not contradict them.

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 short paragraphs with the one-line summary first and the key implementation detail second. Every sentence adds value and there is no filler or repetition.

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?

For a one-parameter creation tool with an output schema and annotations, the description covers what is created, where it is stored, and how its key is generated. It is slightly ambiguous what happens when the same prompt is submitted twice, but that minor gap does not block correct invocation.

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?

The input schema already documents the single 'prompt' parameter with 100% coverage. The description repeats that the prompt is text but adds no new constraints, formatting rules, or edge-case behavior, so it stays at the baseline for schema-covered parameters.

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 opens with a specific action ('Create') and target resource ('Docling document'), and clarifies the input is a prompt string. It also states the document is stored in the local document cache, which narrows the semantics beyond the title. It doesn't explicitly contrast with sibling converter tools, but the prompt-based creation path is sufficiently distinct.

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 text implies use when you need a new Docling document from a prompt, and 'new document' signals creation rather than conversion. However, it never explicitly says when not to use this tool or points to alternatives like convert_document_into_docling_document, so guidance is only implicit.

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