send_chat_message

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

With no annotations, description carries full burden. Discloses key behaviors: optional assignment making it actionable, choice of message vs. post type, and return of created message with id. Does not cover permissions or rate limits, but adequate for main 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?

Two sentences, front-loaded with purpose, no redundant words. Efficiently conveys core function and optional features.

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?

No output schema, but description states return value (message with id). Covers essential aspects for a send-message tool. Missing minor details like whether it requires existing channel membership, but overall complete.

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%, baseline 3. Description adds meaning by explaining 'assignee' as 'turning it into an actionable item' and 'type' as 'message vs. post', enhancing schema definitions.

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 'Send a new message to a Chat channel', specifying verb (send), resource (message), and context (ClickUp Chat v3). Distinct from siblings like create_chat_channel or create_chat_message_reply by focusing on sending a new message.

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?

Describes when to use (sending a new message) and mentions optional features (assignee for action items, type selection). Lacks explicit when-not-to-use or alternatives (e.g., for replies), but context is clear.

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