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

readOnlyHint=true already tells the agent this is a safe read, so the description owes less. It adds useful provenance by naming ClickUp's "Get Filtered Team Tasks" and the underlying REST route GET /team/{team_id}/task, but says nothing about result caps, pagination behavior, or filtering semantics beyond the schema. Adequate but not rich.

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?

Three short fragments, nothing redundant, and the scope statement is front-loaded before the API provenance. Slightly telegraphic (sentence fragments rather than prose) but effectively zero waste.

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 12-parameter filtered-read tool where the schema documents every parameter and annotations cover safety, the description gives enough to route and call correctly. It does not note pagination limits or return shape, but no output schema exists and a task-list return is self-evident.

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 all 12 parameters are already documented in the schema (including sort, due-date bounds, and closed-task handling). The description adds only scope framing (workspace vs spaces/folders/lists) which loosely maps to team_id/space_ids/project_ids/list_ids. 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?

States a specific verb and resource ("Search/filter tasks") plus the scope boundary: workspace-wide with optional narrowing to spaces/folders/lists. This is clear enough to separate it from list-scoped siblings like clickup_get_tasks, though it never names those siblings explicitly.

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 phrase "across a whole workspace (team), optionally scoped to spaces/folders/lists" implies when this tool is appropriate (broad cross-container search), but there is no explicit when-to-use statement or named alternative to clickup_get_tasks. Usage must be inferred from the scope wording.

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