clickup_view_list

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

Describes the return value as a compact array of view objects with id, name, type. No annotations provided, so the description carries the burden. It does not mention any side effects or limitations, but as a read-only list operation, this is acceptable.

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 sentences, front-loaded with purpose and immediately followed by key constraint. No wasted words.

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 no output schema, the description clearly states the return shape. It covers essential scope options and parameter relationships. Could optionally mention if there's pagination or sorting, but not necessary for a simple list tool.

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?

Adds significant meaning beyond the schema by explaining the mutual exclusivity rule and how to obtain IDs from other tools (e.g., clickup_folder_list). Schema coverage is 100%, but description still adds valuable usage context.

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?

Clearly states it lists saved views of various types, attached to specific scopes (space, folder, list, workspace). Differentiates from siblings by specifying the scoping rules.

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?

Explicitly states that exactly one of space_id, folder_id, list_id must be provided, or omit all for workspace-level views. Provides context on when to use each scope, but does not explicitly mention when not to use this tool vs alternatives like clickup_view_get.

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