clickup_list_docs

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Search/list' which implies read-only, but does not explicitly state that it is non-destructive, requires no special auth, or describe any side effects. The minimal disclosure leaves the agent underinformed.

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, concise sentence that front-loads the purpose. Every word contributes to understanding the tool's function with no redundancy.

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 description covers the basic purpose and doc_type filtering but omits details about the limit parameter, output format, and any behavioral guarantees (e.g., read-only). Given the lack of annotations and output schema, the description is adequate but leaves important gaps.

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 low (33%), and the description adds meaning for doc_type by explaining its enum values and default. However, the limit parameter has no description in either the schema or the description, leaving its semantics unclear. The description partially compensates but not fully.

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 tool searches/lists ClickUp Docs and Wikis, with the ability to filter by doc_type. This distinguishes it from siblings like clickup_list_doc_pages (which lists pages within a doc) and clickup_list_tasks (tasks).

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 explicit guidance on using the doc_type parameter to filter results. However, it does not mention when to use this tool versus alternatives like clickup_list_doc_pages or clickup_list_tasks, nor does it state prerequisites or exclusions.

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