clickup_search_tasks

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

With no annotations, the description carries the full burden. It states the tool searches 'entire workspace', implying broad scope unless filtered, which is useful. However, it omits details about pagination, sorting, default behavior, or result limits.

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, front-loaded with the core action. However, it is too brief and sacrifices necessary detail, making it only adequate in structure.

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 has 19 parameters and no output schema, the description is severely incomplete. It does not explain return format, pagination behavior, filtering scope, or how filters combine. An agent would lack essential context for effective use.

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 only 32%, so the description should compensate by explaining key parameters, but it does not mention any. The description adds no semantic value beyond the schema fields, leaving many parameters (e.g., page, order_by) undocumented.

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 'Search tasks across an entire workspace' clearly indicates the verb and resource, but it does not distinguish this tool from sibling 'clickup_get_tasks', which may also retrieve tasks. The scope 'entire workspace' is helpful but lacks differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'clickup_get_tasks' or 'clickup_get_task'. The description does not specify prerequisites, context, or scenarios where searching is preferred over listing.

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