clickup_comment_create

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

The description fully discloses behavioral traits: @mentions are recognized, markdown is not rendered (stored as literal), and the tool returns the created comment object with its new id. Since no annotations are provided, the description carries the full burden and meets it well.

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?

The description is concise with four sentences, each adding value. It is front-loaded with the main purpose and includes important behavioral notes without unnecessary verbosity.

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 creation tool with no output schema, the description covers key aspects: action, mention rendering, markdown limitation, and return value including id for chaining. Minor gaps like error handling or rate limits are acceptable given tool complexity and parameter coverage.

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 description coverage is 100%, so the parameters are already well-documented in the schema. The description adds only the contextual note about the returned id, but does not provide additional meaning beyond what the schema offers per parameter. Baseline 3 is appropriate.

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's action: 'Post a new top-level comment on a ClickUp task.' It distinguishes itself from sibling tools like clickup_comment_reply and clickup_comment_update by specifying 'top-level' and noting the returned id can be used for those tools.

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?

While not explicitly stating when to use this tool versus alternatives, the description implies that for replying (clickup_comment_reply) or updating (clickup_comment_update), the returned id is needed. Context is clear, but no explicit when-not guidance.

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