clickup_doc_add_page

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

With no annotations, the description carries full burden. It discloses that the tool returns the created page object including its id, and mentions optional parameters like team_id defaulting to config. However, it does not discuss error scenarios, required permissions, or rate limits, leaving some behavioral gaps.

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?

Three sentences, no filler. First sentence states primary purpose, second adds markdown/subtitle/parent_page_id details, third describes return value and links to sibling tools. Every sentence is informative.

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's complexity (6 parameters, no output schema), the description adequately explains the return value and relationships to other tools. It lacks details on prerequisites or error handling, but for a create tool this is sufficient.

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 coverage is 100%, and the description adds value beyond schema: explains parent_page_id creates a page tree, content omission creates empty page for later editing, name appears in navigator, team_id defaults to config. This enriches parameter understanding.

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 clearly states the action (create a new page), the resource (inside an existing ClickUp doc), and distinguishes from similar tools by mentioning nesting via parent_page_id and referencing sibling tools like clickup_doc_edit_page and clickup_doc_get_page.

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 explains when to use the tool (to add a page to a doc) and hints at alternatives (nesting with parent_page_id). However, it doesn't explicitly exclude creating a doc itself, which is covered by clickup_doc_create, but the purpose is clear enough to avoid confusion.

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