Deletes a specific Linear comment using its ID. Cleans up issue discussions by removing unwanted or outdated comments.
Delete a comment
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the comment to delete |
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| success | No |
Changes observed during successful MCP inspections.
v1.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide destructiveHint=true and idempotentHint=true, which the description aligns with but does not expand upon. No additional behavioral details (e.g., permissions, cascading effects) are offered.
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?
Extremely concise – a single phrase captures the entire operation. No wasted words. Front-loaded and easy to parse.
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 delete tool with full schema coverage and annotations, the minimal description is viable but lacks any additional context like expected response or error conditions. Could be improved by noting idempotency or success behavior.
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%; the schema's own description for 'id' is 'ID of the comment to delete'. The tool description adds no new semantic information beyond this.
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?
Description is 'Delete a comment' – a clear verb+resource combination that precisely states the tool's function. It distinguishes from siblings like createComment, updateComment, and getComments.
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 on when to use, prerequisites (e.g., must have comment ID), or alternatives. For a destructive operation, this context would help the agent make responsible choices.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.