Get Task Comments

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the behavioral detail that results are one page in reverse-chronological order, which is useful. However, it does not disclose how to navigate pages or what the response structure looks like.

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, front-loaded sentence that conveys the core purpose without extraneous words. Every word earns its place, making it appropriately concise.

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 description gives the essential purpose and useful ordering/pagination information, but lacks details on pagination parameters (start vs start_id), response format, and possible filters. Given the absence of an output schema and zero parameter descriptions, the description leaves meaningful gaps for effective invocation.

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 has zero descriptions for its parameters, and the description only implies task_id via 'from a ClickUp Task'. It does not explain start, start_id, workspace_id, or custom_task_ids, leaving the agent to guess their semantics. This is insufficient compensation for 0% schema 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 precisely states the action ('get'), resource ('comments'), source ('from a ClickUp Task'), and scope ('one reverse-chronological page'). It differentiates from siblings like create_task_comment and get_threaded_replies by focusing on listing comments with specific ordering and pagination.

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 the tool is used to fetch comments on a task, but it doesn't explicitly state when to prefer this over alternatives like get_threaded_replies or when not to use it. No guidance is provided on pagination or filtering scenarios.

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