wp_discard_draft

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

The word 'Delete' indicates destructive behavior, and the mention of 'Prod writes require allow_prod=true' provides a safety guard. While it does not detail permanence or side effects, the key behavioral aspects are covered.

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 concise sentence that conveys the core action and the critical safety condition without any fluff.

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 description is adequate for a simple delete action but lacks context about what 'staged' means, what happens after deletion, and how install relates to the operation. The missing parameter details contribute to a moderate completeness gap.

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 description only touches on allow_prod (in the context of prod writes) and does not explain install or draft_id. With zero parameter descriptions in the schema, the description fails to compensate for the missing semantics of two out of three parameters.

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 states a specific action (Delete) on a specific resource (staged wpops draft) and explicitly contrasts it with publishing, making the purpose clear and distinct from sibling tools like wp_publish_swap.

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 implies when to use this tool (for drafts that should not be published) and includes a key condition for production writes (allow_prod=true). However, it does not explicitly name alternative tools for cases like publishing or editing, leaving some inference required.

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