wordpress_advanced_bulk_delete_posts

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

With no annotations provided, the description carries the full burden. It discloses the batch size constraint (100 posts) and the dual deletion modes (trash vs. permanent). However, it lacks safety context like permission requirements, atomicity guarantees, or what happens to associated comments/meta.

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 efficiently structured in three sentences covering action, modes, and limits. The '[UNIFIED]' prefix appears to be metadata noise but doesn't significantly detract. Information is front-loaded with the core action.

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 the destructive nature, zero schema descriptions, and lack of output schema, the description provides minimum viable coverage (purpose, modes, limits) but omits crucial details like input formats for 'site'/'post_ids', return structure, and partial failure behavior expected for bulk operations.

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 implies the 'force' parameter's behavior through 'move to trash or permanently delete,' it fails to document the 'site' parameter (format unclear) or 'post_ids' array contents (integers? strings?), leaving critical input semantics undefined.

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 'Delete multiple posts at once,' providing a specific verb and resource. It distinguishes from siblings like 'wordpress_delete_post' (single) by emphasizing the bulk nature, and from 'wordpress_advanced_bulk_delete_media/products' by specifying the 'posts' resource.

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 mentions the 100-post limit ('Max 100 posts per request') and hints at the trash vs. permanent delete modes, providing implicit constraints. However, it lacks explicit guidance on when to choose this over single-delete tools or error handling for exceeding the limit.

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