wp_delete_comment

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about whether the comment is trashed or permanently destroyed, whether force is needed, what permissions are required, or whether replies are affected. The only behavioral hint (trash vs permanent) lives in the schema's force field, not the description.

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?

It is short and front-loaded, but this is under-specification rather than conciseness: the single phrase conveys no information an agent could not infer from the tool name alone.

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?

A destructive mutation tool with no annotations, no output schema, and an optional force flag that changes consequences irreversibly needs at least a note on trash-vs-permanent behavior and required capability; the description supplies none of it.

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%, so id, site, and force are already documented in the schema (force explicitly as 'Bypass trash and delete permanently'). The description adds nothing beyond that, so the 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?

"Delete a comment" names a verb and resource but is effectively a restatement of the tool name with no scope, no distinction from the roughly two dozen other delete_* siblings (wp_delete_post, wp_delete_media, wp_delete_category, mcp_delete_widget), and no indication of what deletion means here.

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?

No when-to-use statement, no prerequisites, and no routing to alternatives such as wp_moderate_comments (which can trash/spam a comment) or wp_update_comment. The agent is given nothing to decide between this and sibling comment tools.

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