clickup_chat_message_update

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

No annotations provided, so description carries full burden. It discloses that the text replaces the entire body (not appended), returns the updated object, and that a 403 error occurs for unauthorized users. This covers key behavioral aspects adequately.

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 efficient sentences: first states purpose, second adds authorization constraint, third explains replacement behavior and return type. No fluff, front-loaded with key information. Perfectly concise.

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 simple mutation tool with well-described parameters and no output schema, the description is complete. It covers the operation, prerequisites (authorization), behavior (full replacement), and return value. No gaps given the tool's complexity.

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% with good descriptions for each parameter. The description does not add new meaning beyond what the schema already provides. Baseline 3 is appropriate as schema does the heavy lifting.

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?

Description clearly states the tool edits an existing ClickUp Chat message (verb 'edit', resource 'existing message'). It distinguishes from sibling tools like clickup_chat_message_send (create) and clickup_chat_message_delete (delete) by specifying the action is modification. The scope is precise.

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?

Description provides explicit constraints: only author or admin can edit, others get 403. It implies usage context (must have message_id from list tools) but does not name alternative tools for when to use send or delete instead. Still clear on when to use and authorization requirements.

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