wordpress_delete_post

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

No annotations provided, so description carries full burden. It explains the key behavioral difference between permanent deletion and moving to trash. However, it does not disclose side effects like deletion of related data (comments, meta) or restoration possibilities from trash.

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?

Two sentences, no wasted words. Front-loaded with the action 'Delete a post'. Efficient and direct.

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 no output schema and low complexity, the description covers the essential functionality. Lacks mention of return value or error cases (e.g., post not found), but for a deletion tool this is acceptable.

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 coverage is 0% so description must compensate. It adds meaning to the force parameter ('permanently delete' vs 'moves to trash') but does not describe postId beyond its name and type in schema. The parameter description is helpful for force but postId is left implicit.

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 a post' and explains the two modes via the force parameter: 'Set force=true to permanently delete, otherwise moves to trash'. This differentiates it from sibling tools like wordpress_bulk_delete_posts and wordpress_update_post.

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 like wordpress_bulk_delete_posts or wordpress_update_post (to trash). Does not mention prerequisites, consequences, or when deletion is appropriate.

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