update_chat_message

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

With no annotations provided, the description must convey behavioral traits. It states 'Only the provided fields change', indicating a partial update (PATCH semantics), and notes that it returns the updated message. However, it does not disclose authentication needs, rate limits, or potential side effects. The information is adequate but minimal.

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: the first introduces the action and resource; the second clarifies update behavior and return value. No extraneous information. The key verb 'Edit' is front-loaded, making it efficient for an agent to parse.

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?

Given the simple tool with 5 parameters, 1 required, and no output schema, the description is complete. It clarifies the update semantics (only provided fields change) and states the return value. The agent has enough context to use the tool correctly.

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 the baseline is 3. The description reiterates the partial-update behavior and mentions the fallback for 'team_id', but these are already present in the schema descriptions. It adds no new parameter meaning beyond what the schema provides.

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 verb 'Edit' and the resource 'Chat message', specifying that content and/or resolved status can be modified. It distinguishes from sibling tools like 'send_chat_message' (create) and 'delete_chat_message' by focusing on updating an existing message. The inclusion of 'ClickUp Chat v3' adds version context.

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 description implies usage when wanting to change a message's content or resolution status, but it does not explicitly state when to use this tool versus alternatives (e.g., using 'send_chat_message' for new messages). No exclusions or prerequisites are mentioned, leaving the agent to infer context.

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