create_document

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a possible mutation but does not state defaults, side effects, permission requirements, duplicate handling, or what preview returns. 'Native REST resource API' adds context but little 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 a single front-loaded sentence with no filler. Its compactness comes at the cost of clarity, which keeps it from a 5.

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 tool with three parameters, a nested values object, no annotations, and 0% schema documentation, one sentence is insufficient. Doctype selection, values shape, and confirm semantics are all unexplained. The presence of an output schema reduces the need to describe return values, but the call semantics remain incomplete.

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% for all three parameters. The description never explains doctype, values, or confirm, nor does it clarify the shape of the nested values object. 'Preview or create' faintly gestures at confirm but does not document it.

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 states a specific verb ('create') and resource ('document'), making the core purpose clear. However, 'Preview or create' introduces ambiguity about whether the default behavior is a write, and no sibling tool is named to distinguish it from update_document or get_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?

There is no explicit when-to-use or when-not-to-use guidance. The word 'preview' hints at a non-committal mode but is never connected to the confirm parameter, and there is no advice to call get_doctype_schema first to discover required fields.

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