clickup_update_list

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

With no annotations provided, the description carries the full burden. It does disclose a genuine behavioral trait — partial update semantics ("Only specified fields updated") — but says nothing about whether the change is reversible, permission/auth requirements, or whether the status value must exist in the list's configured statuses. Adequate but thin for a mutation tool with zero annotation coverage.

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 sentences, front-loaded with purpose, then requirement, then the sibling pointer. No filler and nothing repeated from structured fields.

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 essentials for invocation (ID source, required inputs, partial-update behavior) but omits what happens on invalid status values or what the update affects downstream, and there is no output schema to fill that gap. Sufficient to call, not sufficient to predict consequences.

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 baseline is 3. The description adds real value beyond the schema by imposing a constraint the schema does not encode: at least one of name/content/status must be supplied even though only list_id is required.

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?

Opens with a specific verb+resource ("Update a ClickUp list") that separates it cleanly from clickup_update_task and clickup_update_folder. It also names the read sibling clickup_get_list, making the read/write split obvious, though it does not spell out which update fields make it distinct beyond listing three.

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 the precondition (list_id plus at least one update field) and routes the agent to clickup_get_list when only a list name is known. It lacks an explicit "do not use when..." statement, but the context is clear enough to select correctly.

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