clickup_get_comments

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

The description lacks annotations, so it must disclose behavior. It mentions pagination with 25 per page, but does not specify if it returns only top-level comments (given the existence of get_replies), ordering, or any side effects. The behavioral disclosure is 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?

The description is a single sentence that conveys all essential information without redundancy. It is efficient and front-loaded, earning its place.

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 read operation with no output schema, the description provides enough information for an agent to use the tool correctly. It could mention the order or type of comments, but completeness is adequate given low 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 parameter descriptions. The description adds context about pagination behavior ('paginated, 25 per page'), which clarifies the purpose of 'start' and 'start_id' parameters beyond the schema.

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 'Get comments on a task', specifying the action and resource. It also notes pagination with 25 per page, which distinguishes it from sibling tools like clickup_create_comment (write) and clickup_get_replies (replies to 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?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description does not mention when not to use it or suggest other tools for related operations, such as creating or updating comments.

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