wordpress_delete_comment

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete a comment' implies a destructive mutation, but the description doesn't mention whether deletion is permanent or reversible, what permissions are required, whether there are rate limits, or what happens to associated data. For a destructive operation with zero annotation coverage, this is dangerously inadequate.

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?

While technically concise with just three words, this is a case of under-specification rather than effective conciseness. The description doesn't earn its place by providing necessary information - it's too brief to be helpful. A proper description would need to be longer to be useful.

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?

This is a destructive mutation tool with 2 undocumented parameters, no annotations, and no output schema. The description provides only the most basic action statement without any context about behavior, parameters, usage, or results. For a tool that permanently deletes content, this level of documentation is completely inadequate and potentially dangerous.

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 schema has 0% description coverage, meaning neither parameter (commentId, force) is documented in the schema. The description provides no information about these parameters - it doesn't mention that commentId is required, what format it should be in, what the 'force' parameter does, or when to use it. This leaves both parameters completely unexplained.

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 'Delete a comment' is a tautology that essentially restates the tool name 'wordpress_delete_comment'. It specifies the verb 'delete' and resource 'comment', but doesn't differentiate from sibling deletion tools like wordpress_delete_post or wordpress_delete_user, nor does it provide any additional context about what kind of comment is being deleted.

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 absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing comment ID), no indication of when to use this versus other deletion tools, and no warnings about consequences. This leaves the agent with no usage context.

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