clickup_doc_pages

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns an array of page objects with specific fields (id, name, sub_title, parent_page_id, optionally content) and that pages are ordered by tree position. It does not mention rate limits, permissions, or what happens on invalid doc_id, but the core behavior is well described.

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 three tightly worded sentences. The first states the purpose, the second lists return fields, and the third adds ordering detail. No superfluous information.

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 list tool without an output schema, the description adequately explains the return format and ordering. However, it lacks details on pagination (if applicable) and error handling. Considering the tool's simplicity, this is mostly complete.

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?

The input schema has 100% description coverage, and the tool description adds minimal value beyond the schema. It indirectly references the content parameter by mentioning 'optionally content' in the return format, but does not provide new meaning. Baseline 3 is appropriate.

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 identifies the verb 'List' and the resource 'pages inside a ClickUp doc'. It also mentions including nested subpages, which distinguishes it from sibling tools like clickup_doc_get_page (single page) or clickup_doc_get (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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it compare with sibling tools such as clickup_doc_get_page, clickup_doc_add_page, or clickup_doc_edit_page.

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