runrunit_list_task_comments

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'List all comments.' It does not state whether the operation is read-only, whether pagination or ordering applies, what permissions are required, or what the response shape looks like. The word 'List' implies a read operation, but that is not explicitly confirmed or elaborated.

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, short sentence with no filler or redundant wording. It front-loads the action ('List all comments') and the resource ('a task in Runrun.it'), making it efficient and easy to scan.

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 definition is minimal and lacks important behavioral context such as return format, pagination, read-only status, and differentiation from sibling comment tools. Since there are no annotations and no output schema, the description alone is not enough for an agent to understand the full behavior of the tool.

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?

The only parameter, task_id, is fully described in the input schema as 'Task ID' with type number, so schema coverage is 100%. The description does not add any extra meaning about where the task_id comes from or how it is used, but because the schema already documents the parameter adequately, this is acceptable.

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 action ('List all comments') on a clear resource ('a task in Runrun.it'), so the tool's primary purpose is immediately understandable. However, it does not explicitly differentiate itself from sibling comment tools like runrunit_get_comment or runrunit_create_comment, relying mostly on the tool name and the word 'all' for distinction.

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 guidance is provided about when to use this tool versus alternatives such as runrunit_get_comment for a single comment or runrunit_list_tasks for finding tasks. The description simply states what the tool does, leaving the agent to infer the appropriate use case without any exclusions, prerequisites, or routing hints.

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