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

Annotations carry the only real behavioral signal (destructiveHint=true, title), and the description's 'WRITE:' prefix largely duplicates it. It adds the concrete endpoint, which is mildly useful, but says nothing about side effects such as notifications, webhooks, or permission requirements for a mutation tool.

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 clauses, zero filler, and the most decision-relevant fact (WRITE, create task in a list) is front-loaded, with the path-param gotcha surfaced before the endpoint reference.

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 an 11-parameter tool with no output schema, the schema already documents all fields and the description covers the two most error-prone points (required name, list_id placement). It stops short of indicating what comes back (e.g. the new task id) or any permission prerequisite, which would be the only additions left.

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 100%, so every parameter is already documented, including the note that list_id is a path param. The description restates that same routing fact and the name-required rule, adding emphasis but no detail the schema lacks. Baseline 3 is correct.

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 ('create a new task in a list') and prefixes it with 'WRITE:' so the agent can instantly separate it from read siblings like clickup_get_task or clickup_search_tasks. Also names the exact REST endpoint, removing any ambiguity about what the call does.

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 'WRITE:' marker plus the endpoint imply when this tool applies, and it flags that `name` is required. But it never names an alternative (e.g. clickup_update_task for modifying existing tasks, or create_task_comment for adding notes), so the agent must infer the boundary itself.

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