wp_publish_swap

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

With no annotations, the description carries the transparency burden and does disclose key side effects: copies content onto live_id, purges cache, deletes the draft, and probes the public URL. It also notes the prod guard (allow_prod=true), but it does not mention authentication, error behavior, or what happens if verification fails.

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 compact and front-loaded, with the main purpose in the first sentence and supporting operational details in the second. It contains no redundant or irrelevant content.

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?

It covers the main workflow and side effects, but it omits output/return behavior, error/verification failure handling, and the meaning of install. Given the absence of an output schema and annotations, these gaps reduce completeness.

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 provides no parameter descriptions, but the narrative explains live_id as the target live post, draft_id as the draft being copied/deleted, and allow_prod as a production-write guard. The install parameter remains unexplained, so coverage is not complete.

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 opens with a specific verb and resource: 'Promote a staged draft onto the live post' and clarifies the scope by mentioning draft deletion and verification. It is distinguishable from sibling tools like wp_discard_draft and wp_edit_page, though it does not explicitly name an alternative.

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 the use case ('Promote a staged draft') and describes the sequence of operations, but it does not explicitly state when to choose this tool over alternatives such as wp_edit_page or wp_discard_draft.

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