Delete Comment

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

With no annotations provided, the description must disclose behavioral traits. It does reveal the ownership restriction, which is important. However, it omits other relevant behaviors such as the irreversibility of deletion, potential error cases, or any cascade effects, leaving the agent with incomplete behavioral information.

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 two short sentences: the first defines the core action, the second adds a critical usage constraint. It is front-loaded, free of fluff, and every word contributes meaningful guidance.

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 simplicity of the tool, the presence of an output schema (which clarifies return values), and a well-described parameter schema, the description is largely complete. The only gap is a lack of explicit note about deletion being permanent, but for a straightforward delete operation, the existing description suffices.

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 already provides clear descriptions for both parameters (issueId and commentId), achieving 100% coverage. The tool description adds no additional parameter-level meaning, so it meets the baseline for well-documented schemas without further enhancement.

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 clearly states the action (delete) and the resource (a comment from an issue). It also adds a distinguishing constraint ('You can only delete your own comments'), effectively separating it from sibling comment tools like updateComment or addComment.

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 a clear usage context (deleting a comment) and an explicit exclusion (only your own comments), which guides when to use this tool. However, it does not mention alternatives like updateComment for editing or listComments for viewing, so it falls short of a perfect score.

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