clickup_doc_get_page

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

No annotations are provided, so the description carries full burden. It states the tool fetches data (implied read-only) and returns a page object with content, which covers basic behavior. However, it lacks details on permissions needed, error conditions, rate limits, or pagination (though likely not needed for a single page).

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 two sentences: the first states the purpose and returned data, the second provides usage guidance. Every sentence adds value with zero waste, and it's front-loaded with the core functionality.

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 read operation with no annotations and no output schema, the description is fairly complete: it states what it does, what it returns, and prerequisites. However, it could benefit from more behavioral context (e.g., error handling, auth requirements) given the lack of annotations and output schema.

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%, so the schema already documents all three parameters with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, but it does imply the relationship between 'doc_id' and 'page_id' through the prerequisite guidance.

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 specific action ('Fetch a single page'), the resource ('from a ClickUp doc'), and the returned data ('full markdown content, title, subtitle, and parent-page link'). It distinguishes from sibling tools like 'clickup_doc_pages' (which lists pages) and 'clickup_doc_get' (which likely gets the doc itself).

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 explicitly states when to use this tool ('Use clickup_doc_pages to list all pages in a doc first'), providing a clear prerequisite. It also distinguishes from 'clickup_doc_pages' by specifying this fetches a single page with full content versus listing pages.

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