wordpress_delete_post

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

No annotations are provided, so the description carries the full burden. It discloses the two operation modes: force=true permanently deletes, force=false moves to trash. This is essential for a destructive action. It also states the return as 'Deletion confirmation,' providing basic feedback context.

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 and well-structured with Args and Returns sections. Every line contributes to understanding the operation, with no extraneous information or redundancy.

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 simplicity (2 parameters) and the presence of an output schema, the description adequately covers the core behavior and parameter effects. It does not mention potential errors or side effects (e.g., deletion of related revisions), but these are not necessary for basic 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 compensates by explaining post_id as 'Post ID to delete' and force as 'If true, permanently delete. If false, move to trash.' This adds meaning beyond the bare schema types. However, it does not mention the default value of force (false) explicitly, though it can be inferred.

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 explicitly states 'Delete or trash a WordPress post,' clearly specifying the action (delete/trash) and resource (post). It distinguishes from sibling tools like wordpress_delete_page and wordpress_delete_media by naming the resource type directly.

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 does not provide explicit guidance on when to use this tool versus alternatives. Usage is implied by the tool name and the clear resource reference, but no exclusions or recommendations are offered for distinguishing between post, page, media, or comment deletion tools.

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