Delete comment

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description contributes only the ambiguous 'pending' scope note; it never says whether the deletion is permanent, what happens if the comment is already published, or what error to expect.

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?

A single front-loaded sentence with no waste, but its brevity comes from under-specification rather than discipline. It leaves out scope and effect details an agent needs.

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 destructive mutation with no output schema and 0% parameter documentation, the description should cover irreversibility, failure modes, and ID sourcing. None of that is present; only the destructive annotation hints at impact.

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% for the single required parameter, commentId, so the description carries the full burden. It says nothing about the ID format, where the ID comes from (e.g., list_comments/get_comment), or whether the ID must refer to a pending 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 verb+resource ('Delete a ... comment') is specific and distinguishable from siblings like delete_post, delete_media, or update_comment. However, the qualifier 'pending' is left unexplained, so an agent cannot tell whether the tool only works on pending comments or also removes published ones.

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 guidance on when to use this versus update_comment, list_comments, or other deletion tools, and no preconditions are stated. The only contextual hook is the unexplained 'pending' qualifier.

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