wordpress_bulk_delete_posts

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions deletion but doesn't disclose if posts are permanently removed, if there's a trash/recovery mechanism, what permissions are required, or potential side effects (e.g., breaking links). The 'force' parameter hints at behavior, but the description doesn't explain it.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action ('Delete multiple posts') and adds clarifying detail ('in one operation') without redundancy. Every word serves a purpose.

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 tool's complexity (destructive bulk operation), lack of annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't cover behavioral risks, parameter meanings, expected outcomes, or error conditions, leaving the agent poorly informed for safe invocation.

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%, so the description must compensate but adds no parameter information. It doesn't explain 'postIds' (e.g., format, source, limits) or 'force' (e.g., bypassing trash, irreversible deletion). For a tool with 2 required parameters, this leaves significant gaps in understanding inputs.

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 verb ('Delete') and resource ('multiple posts'), specifying it's a bulk operation ('in one operation'). It distinguishes from sibling tools like 'wordpress_delete_post' (singular) and 'wordpress_bulk_delete_media' (different resource), but doesn't explicitly differentiate from other bulk operations like 'wordpress_bulk_update_posts' beyond the action.

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?

No guidance on when to use this tool versus alternatives is provided. It doesn't mention prerequisites (e.g., needing post IDs), contrast with single-delete tools, or specify scenarios like cleanup vs. selective removal. The description only states what it does, not when to apply it.

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