outline_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 fails to mention what the tool returns (document ID, full object, or nothing), error handling for invalid parentDocumentIds, side effects of publishing, or required authentication/authorization levels.

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 words. It is appropriately concise, though it errs on the side of minimalism given the tool's complexity. The structure is correct with the action verb leading.

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 tool has 5 parameters including optional nesting (parentDocumentId) and publishing logic (publish), plus no output schema or annotations, the 6-word description is insufficient. It omits return value semantics, hierarchical document relationships, and default behaviors.

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 structured schema already documents all parameters (title, text, collectionId, parentDocumentId, publish) adequately. The description adds no parameter-specific guidance, but the baseline score of 3 applies given the comprehensive 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?

The description uses a specific verb ('Create') and resource ('document') and identifies the target system ('in Outline'), making the basic purpose clear. However, it does not distinguish from sibling tools like outline_update_document or outline_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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when to create vs. update), nor does it mention prerequisites such as needing a valid collectionId or permissions to publish.

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