wp_posts_delete

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

With no annotations present, the description carries the full burden. It discloses the recoverable nature of trash, the irreversible permanent deletion, and the additional safety confirm mechanism. This gives the agent a good understanding of consequences, although it doesn't cover edge cases like deleting already-deleted posts.

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 extremely concise, front-loaded with the core action, and every sentence adds value. It packs essential behavioral details into two sentences without any fluff or repetition.

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 3-parameter delete tool with no output schema and no annotations, the description covers the critical aspects: default behavior, permanent deletion path, and required confirm format. Minor omissions like error handling or permissions are not critical for basic invocation, but the description could have noted the irreversibility explicitly. Overall, it is well-rounded.

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?

The schema has 0% coverage, so the description must compensate. It explains 'force' and 'confirm' in detail, including the exact format 'DELETE_PERMANENTLY_<id>', but does not explicitly describe 'id'. That said, 'id' is self-evident from context and the schema's basic type, so the non-obvious parameters are well handled.

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's action with a specific verb and resource ('Delete a post'), and immediately distinguishes between the default trash behavior and permanent deletion, making its purpose unambiguous and distinct from sibling tools like wp_posts_update or wp_posts_publish.

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?

It provides clear context on when to use the default trash path versus the permanent deletion path, including the required confirm string format and MODE=full prerequisite. However, it does not explicitly mention alternative tools or when-not-to-use, so it stops short of a 5.

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