create_document

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

No annotations are present, so the description carries the disclosure burden. It explains the return shape, the doc_id-based workflow, and show behavior in detail, including live mode, defaulting, off-screen building, and headless-server no-op. It stops short of covering persistence or error behavior, but the critical behavioral traits are disclosed.

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 purpose is front-loaded in the first sentence, and each parameter has a focused explanation. The show explanation is slightly longer than strictly necessary, but every sentence adds meaningful information.

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 two-parameter creation tool, the description covers parameters, return value, and the doc_id lifecycle handoff. It does not mention persistence, file naming, or how it relates to open_document, but these are secondary for a create call.

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 0%, so the description fully compensates. It documents the allowed kind values, the return relationship to kind, and the show parameter's meaning, defaults, and runtime context. This goes well beyond the bare 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?

States a specific verb ('Create'), a specific resource ('new empty LibreOffice document'), and enumerates document kinds. It also names the return value and the doc_id handoff, which distinguishes it from sibling tools like open_document and save_document.

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 usage as the starting point for a new document ('pass doc_id to subsequent tools'), giving some context. However, it does not explicitly say when to use this tool versus open_document for existing documents, or mention any exclusions.

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