clickup_create_comment

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

No annotations are provided, so the description carries the full behavioral burden. It discloses Markdown support and threaded-reply behavior, but says nothing about permissions, notification semantics, rate limits, mutation effects, or what happens on failure for a write operation.

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 three short sentences, front-loads the core action, and immediately clarifies Markdown support and threading. It contains no filler or repetition.

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?

The schema is rich and fully described, and the description covers the key targeting and threading mechanics. Still, for a mutation tool with no annotations or output schema, it omits important context such as sibling disambiguation and notification or permission behavior, so it is only adequately 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 description coverage is 100%, so all seven parameters are already well documented in the schema. The description reinforces entity_type, entity_id, and reply_to_id, but adds no meaningful parameter semantics beyond the schema, which matches the baseline for high coverage.

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 states a specific verb and resource: creating a comment or threaded reply on a task, list, or view. It is clear what the tool does, but it does not distinguish itself from the sibling clickup_create_task_comment, which likely overlaps for task comments.

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?

It gives usage mechanics for target selection (entity_type + entity_id) and threading (reply_to_id), which implies when those options apply. However, it does not state when to use this versus clickup_create_task_comment or when not to use it, leaving the main alternative implicit.

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