wp_delete_post

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

The description mentions 'safety confirmations and detailed feedback' but does not specify what those entail. It also explains the force parameter for permanent deletion. With no annotations, more detail on consequences (e.g., whether post data is recoverable from trash) would improve transparency.

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 concise with a clear purpose and structured usage examples. The phrase 'Includes safety confirmations' is slightly vague but overall 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?

Covers basic behavior and options with examples, but lacks details on return values or feedback format given no output schema. For a deletion tool, this is adequate but not fully complete.

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 100%, and the description does not add significant meaning beyond the schema. The examples illustrate usage of 'id' and 'force', but the schema already describes them adequately.

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 clearly states the tool deletes a WordPress post and distinguishes it from siblings like wp_delete_page by specifying 'post'. It also covers deletion options (trash/permanent).

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?

Provides explicit usage examples for trash, permanent deletion, and bulk operations, giving clear context for when to use each option. However, it does not explicitly contrast with sibling tools like wp_delete_page.

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