wrike_list_comments

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

No annotations are provided, so the description carries the full burden. It only states 'List comments on a task or folder' and does not disclose pagination behavior (e.g., how 'limit' interacts), ordering, whether both taskId and folderId can be provided, or whether HTML vs plain text affects the response. For a read operation, this is a significant gap.

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 concise sentence that front-loads the key information: what the tool does and on what resource. There is no wasted text or redundancy.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the one-sentence description is insufficient. It does not explain pagination, parameter interactions, or expected return behavior. For a list operation with such parameters, more detail is needed to ensure correct usage.

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 input schema descriptions cover 100% of parameters, so the baseline is 3. The description does not add any meaning beyond the schema—it only clarifies the resource type ('task or folder') but does not explain relationships between parameters (e.g., mutual exclusivity of taskId and folderId) or date range semantics.

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 uses a specific verb ('List') and a specific resource ('comments') with a clear scope ('on a task or folder'). This distinguishes it from sibling tools like wrike_get_comment (single comment), wrike_create_comment, wrike_update_comment, and wrike_delete_comment.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that wrike_get_comment retrieves a specific comment, nor does it explain whether this tool should be used for listing all comments on a task versus a folder. There are no exclusions or alternative tool references.

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