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

Annotations already flag this as non-read-only, destructive, open-world, and non-idempotent. The description adds important behavior beyond that: it requires moderate_comments capability and edit rights on the comment's post, and in the Royally flow it merely queues the request until a person approves, with no site change until then.

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 action is front-loaded and the description stays short with no filler. The parenthetical site note interrupts the flow slightly, but the overall structure remains efficient.

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 mutation-like action with a human approval gate, the description covers the key operational facts: permissions and the fact that no site change happens until a person approves. It omits return value and how to track the pending approval, but it remains adequate for the tool's complexity.

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 coverage is 50%; site_id is documented in the schema, while comment_id has no schema description. The description adds only the implication that comment_id refers to a pending comment, but does not explain format, lookup, or how to identify the correct 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 description opens with a precise verb-resource pair: 'Approve a pending comment.' This clearly separates the tool from siblings such as wp_spam_comment, wp_trash_comment, wp_delete_comment, and wp_get_pending_comments without requiring the schema to be read.

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?

Usage is implied by the action ('approve a pending comment'), but the description does not explicitly say when to choose this tool over spam/trash/delete alternatives or what prerequisites must be checked first. The permission note is helpful context, not usage routing.

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