wp_delete_post

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

No annotations are provided, so the description carries the full behavioral burden. It mentions that credentials are required, but it does not disclose whether the deletion is permanent, whether it moves to trash, what the 'force' parameter does, or what side effects might occur. For a destructive tool this is a significant transparency gap.

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 description is short and front-loaded, with the core operation stated first and the credential prerequisite in a second sentence. Both sentences are relevant, though the description could be expanded without becoming overly verbose.

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?

Given that this is a destructive operation with no annotations and no output schema, the description is incomplete. It does not explain the behavior of 'force', whether the action is reversible, what the response looks like, or how this compares to deleting a page or updating a post's status.

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%, and the description adds no meaning for the 'id' or 'force' parameters. An agent cannot determine what 'force' does or why 'id' is required beyond the raw type information in the schema.

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 a specific verb ('Delete') and a specific resource ('a WordPress post'), clearly distinguishing it from sibling tools like wp_get_post, wp_update_post, and wp_create_post. It also differentiates from wp_delete_page via the 'post' target.

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 implies the tool should be used when a WordPress post needs deletion, but it does not explicitly discuss when to prefer this over related tools such as wp_update_post or wp_delete_page. It also does not mention alternatives or exclusion conditions.

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