clickup_update_view

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

The description explains the replacement semantics (no partial update) and error codes (404, 400). Annotations already indicate idempotent and non-destructive, but the description adds important context about the full-replacement behavior.

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?

Well-structured with clear sections: introductory sentence, behavior note, usage guidelines, return value, example, and error handling. No wasted words, front-loaded with core action.

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?

Covers key behavioral aspects (full replacement), prerequisites (call get_view), pitfalls (no hierarchy change), return type, and error handling. Output schema exists so return details are handled. Complete for agent usage.

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?

While the input schema has detailed descriptions, the description adds value by explaining the need to resupply parent_id/parent_type and config blocks from get_view. It clarifies the full-replacement requirement beyond the schema's field descriptions.

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 clearly states the tool renames a view and replaces its grouping/sorting/filters/columns/settings. It distinguishes from siblings like clickup_create_view and clickup_delete_view by specifying the update action and noting the API's full-replacement behavior.

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?

Explicit 'When to Use' and 'When NOT to Use' sections. It advises using clickup_get_view first and warns against trying to move a view across hierarchy levels, directing to delete/recreate instead.

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