deletePullRequestComment

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds no additional behavioral context (e.g., permanence, permission requirements, effect on replies). It simply restates the operation, so it does not exceed what annotations already provide.

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, direct sentence with no filler. The essential action is front-loaded and clear.

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 a simple delete operation; the schema covers input, annotations cover safety, and the description states the action. However, it lacks any information about return values, error conditions, or preconditions beyond what is structurally stated. For a destructive tool, a note about irreversibility would improve completeness, but it is not strictly necessary given the annotation. Overall, adequate but not rich.

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 has 100% description coverage for all four required parameters (owner, repo, pull_number, comment_id). The description doesn't mention parameters but the schema fully documents them, so the description adds no extra meaning; baseline 3 applies.

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 the specific verb 'Delete' and specifies the resource 'discussion comment on a pull request.' It is clear what the tool does and is distinct from siblings like addPullRequestComment and updatePullRequestComment, though it does not explicitly name them.

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 only states the action; it provides no guidance on when to use this tool versus alternatives (e.g., update or add), no prerequisites, and no mention of conditions like ownership or permissions. An agent must infer usage solely from the name and sibling list.

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