clickup_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 behavioral burden. It says nothing about permission requirements, what visibility settings actually do (PUBLIC vs PERSONAL vs HIDDEN), whether the parent container must exist or be accessible, or what is returned after creation — all relevant for a mutation tool.

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?

Two short sentences with the core action front-loaded. The second sentence is largely redundant with the schema's required list, but the overall size is appropriate and wastes no space.

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?

The tool has five parameters, a nested parent object, and no annotations or output schema, so behavioral context matters. The schema fully documents parameters, but the description omits what a created document contains, how visibility affects access, and how the parent id/type must correspond — leaving an agent to guess at runtime behavior.

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 100%, including enum values for parent.type and visibility, so the schema does the heavy lifting. The description's mention of name/parent/visibility/create_page is redundant with the schema and adds no new meaning; workspace_id is never referenced.

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 gives a specific verb and resource ('Create a document') and names the valid parent container types (space, folder, list), which separates it from clickup_create_document_page or clickup_create_list. It does not explicitly name the sibling it differs from, so an agent must infer that this creates the document container rather than a page inside one.

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 second sentence only restates which parameters are required, which the schema already enforces. There is no guidance on when to use this versus clickup_create_document_page, clickup_create_folder, or clickup_create_list, and no prerequisites or exclusions are mentioned.

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