delete_work_item_comment

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no statement about permanence, recoverability, permission requirements, or side effects on comment threads, so it earns no credit for extra behavioral context.

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?

One short, front-loaded sentence with zero filler, so it is not verbose. The terseness is under-specification rather than efficiency, though, and nothing is prioritized because only one fact is conveyed.

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 tool is simple and annotations plus schema cover the parameter and the destructive/idempotent profile, so an agent can call it correctly. What is missing is context an agent would want before a destructive call: whether the delete is permanent or reversible and whether child replies are removed.

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 100% for the single commentId parameter ("Comment UUID."), so the schema already carries the parameter meaning. The description adds no format or sourcing detail beyond the schema, which matches the baseline 3 for high-coverage schemas.

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 verb ("Delete") and resource ("a work item comment"), so the operation is identifiable. However, it is essentially the tool name restated with no added scope detail — nothing about whether replies/threads are affected or whether deletion is permanent — and it offers no differentiation from siblings such as delete_work_item or delete_attachment beyond the name itself.

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?

There is no when-to-use guidance and no stated alternatives or exclusions. An agent is left to infer that this applies only to comments and not to work items, attachments, or autotests, purely from the tool name.

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