Update a post / page

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

With no annotations, the description carries the transparency burden. It discloses the partial-update behavior and warns that content replaces the whole body, which is a destructive side effect. It does not mention auth or response format, but the key behavioral traits 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 two sentences, front-loaded with the core purpose, and every clause adds value. It is concise without sacrificing essential caveats, making it easy for an agent to parse quickly.

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 has 16 parameters, no output schema, and no annotations. The description covers the update semantics and content caveat but omits return value, required id emphasis, status defaults, and interaction with other parameters. For a tool this complex, the description leaves significant gaps.

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 only 50%, and the description adds little beyond what the schema already states about content. It reinforces the content replacement behavior but does not clarify other undocumented parameters like slug, tags, title, author, parent, excerpt, template, or categories, leaving them ambiguous.

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 tool updates an existing item, distinguishing it from create/delete siblings. The title 'Update a post / page' and the phrase 'existing item' provide a specific verb and resource, though 'item' is slightly generic without the title.

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 provides explicit usage context: only passed fields are changed, and it advises reading content with wp_get_content before partial edits. This gives clear guidance for a common use case, though it does not explicitly exclude when to use create/delete instead.

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