delete_work_item_comment

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

Annotations already mark this as destructive (destructiveHint=true) and not read-only. The description adds no extra behavioral context: it does not state that deletion is permanent, mention cascading effects (e.g., replies), or note permission requirements. It simply restates the action, adding no value beyond the annotations.

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, direct sentence with no filler words. It is front-loaded with the verb and object, making it easy to scan. However, it is concise to the point of being under-specified, sacrificing useful context for brevity, which slightly lowers the score.

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?

With three required parameters and no output schema, the description should at least note that all three IDs are needed to identify the comment, and perhaps mention that the deletion is scoped to a specific work item and project. It does not, leaving the agent to infer this from sibling tool patterns. The tool is simple, but the description is too thin to be fully self-sufficient.

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 description coverage is 0%, and the description does not compensate. It mentions 'a comment' and 'a work item' but does not explain that all three parameters (comment_id, project_id, work_item_id) are required and how they scope the deletion. The parameter names are somewhat self-explanatory, but the description fails to clarify why project_id and work_item_id are necessary or how they relate to the comment.

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 'delete' and clearly identifies the resource as 'a comment from a work item', which distinguishes it from sibling tools like create_work_item_comment, update_work_item_comment, and list_work_item_comments. No ambiguity about what the tool does.

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 update_work_item_comment is for editing, nor does it note conditions like the comment existing or being owned by the caller. There is no contextual advice whatsoever.

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