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 two behavioral modes: moving to trash (force=false) or permanent deletion (force=true). However, it omits important details such as reversibility of trash, required permissions, potential side effects (e.g., on comments, attachments), and how errors are handled.

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 very concise: two sentences that state the action and explain the key parameter behavior. No unnecessary words, and the important information is front-loaded.

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?

The tool is simple with two parameters, and an output schema exists (so return values are covered). The description explains the core behavior adequately. It is nearly complete, but could mention that the post must exist or what happens on failure.

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 100% with both parameters described. The description adds value beyond the schema by explaining the behavioral difference between force=false and force=true: 'If force=false, post is moved to trash. If force=true, post is permanently deleted.' This clarifies the effect of the parameter beyond its type and default.

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 a post in WordPress site.' This defines the action (delete) and resource (post). The sibling tools include other CRUD operations like create_post, update_post, retrieve_post, list_posts, so the purpose is well-distinguished.

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, nor does it mention prerequisites or error handling. However, the context of sibling tools and the straightforward nature of deletion make the usage clear enough for a basic scenario.

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