clickup_space_update

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

With no annotations, description explains archiving behavior (hidden but retains data) and return value (updated space object). Lacks auth or rate limit details, but adequate.

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?

Two sentences, no waste. First states purpose and operations, second adds crucial behavioral nuance.

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?

Simple tool with 4 params well-documented in schema. Description covers behavior and output completely. No gaps.

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 has 100% description coverage. Description adds extra context about archiving vs deletion and return value, going beyond schema.

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?

Clearly states 'Modify a ClickUp space' with specific operations: rename, toggle privacy, archive/unarchive. Distinguishes from create, delete, get, list siblings.

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?

Provides context about archiving as a reversible alternative to deletion, guiding when to use this tool over delete. No explicit when-not, but purpose is clear.

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