wordpress_delete_post

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

With no annotations provided, the description carries the full burden. It explains the trash vs. permanent delete distinction but omits critical behavioral details for a destructive operation: reversibility of trash, cascading effects on comments/meta, error handling for non-existent posts, and authentication requirements.

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?

Extremely concise at two sentences with no filler. The '[UNIFIED]' prefix appears to be metadata noise but doesn't significantly detract. Every word earns its place by conveying the core action and dual-mode capability.

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 destructive 3-parameter tool with zero schema annotations and no output schema, the description adequately covers the core behavioral modes (trash vs. delete) but leaves significant gaps around parameter semantics, safety warnings, and error conditions that should be addressed.

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%, requiring the description to compensate. While it vaguely alludes to the 'force' parameter's purpose ('permanently delete'), it fails to document the 'site' parameter (format: URL, slug, ID?) or 'post_id' expectations at all.

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?

Description clearly identifies the action (delete/trash) and resource (WordPress post), distinguishing it from siblings like wordpress_delete_page or wordpress_delete_media. However, it doesn't clarify the specific behavior differences between this and wordpress_advanced_bulk_delete_posts.

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?

Implies the choice between trashing and permanent deletion via 'Can permanently delete or move to trash,' but offers no explicit guidance on when to use each mode or when to prefer the bulk delete sibling alternative.

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