Update WordPress Post

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

Annotations already mark this as destructive (destructiveHint=true) and not read-only. The description adds non-obvious behavioral context: partial/merging updates rather than full replacement, and the content_path override behavior. This goes beyond annotation-only knowledge.

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 core purpose, followed by a clearly organized args list and a returns line. Every sentence and bullet carries useful information with zero waste.

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?

For a 13-parameter tool with no output schema, the description provides a solid overview, explicit merge behavior, parameter categorization, and return type. It doesn't detail error cases, but annotations cover destructive/idempotent hints and the schema fully documents parameters, making it adequately complete.

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 100%, so the baseline is 3. The description adds a valuable cross-reference to wp_create_post ('same shape as wp_create_post') and clarifies that content_path overrides content, enriching context beyond the schema's individual parameter descriptions.

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 'Update an existing post' with a specific verb and resource, distinguishing it from sibling update tools like wp_update_page, wp_update_widget, and wp_update_media. It also implicitly contrasts with wp_create_post by requiring an existing post ID.

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 explains partial update semantics ('Only the fields you pass will change; omitted fields preserve their current values') and requires an id, which implies use on an existing post. However, it does not explicitly mention alternatives such as wp_bulk_update_posts or provide when-not-to-use guidance, so usage direction is implied rather than explicit.

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