wp_pages_update

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that only provided fields change (idempotent partial update) and that status transitions to publish/future/private require a publish tier (authorization constraint). This adds meaningful transparency beyond the schema, though it could also mention error handling or general permissions.

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?

Three sentences, each with a distinct purpose: defining the operation, noting the partial-update behavior, and providing usage guidance for specific parameters. No filler or redundancy.

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?

Given the tool's 13 parameters, no output schema, and no annotations, the description covers core update semantics and one usage tip, but omits details about return values, error cases, and general authorization. It is adequate but not fully complete for an agent to use confidently in all scenarios.

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 0%, so the description must compensate. It adds semantics for only two parameters: "parent" (re-parenting) and "status" (publish tier requirement). The remaining 11 parameters (e.g., title, content, featured_media) lack any explanatory context in the description, leaving a significant gap.

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 the specific verb "Partially update" and resource "existing page by id", clearly distinguishing it from create/delete operations. The phrase "Only provided fields are changed" further clarifies it is a PATCH-like update, not a full replacement.

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 clear context: it specifies the partial update behavior and gives a prerequisite (publish tier for certain status transitions). It also advises on using the parent parameter for re-parenting. However, it does not explicitly mention when to prefer this tool over sibling tools like wp_posts_update, so it falls short of a 5.

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