wp_update_page

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

With no annotations provided, the description carries the full burden. It discloses an important behavioral trait (snapshot creation before update), which is not in the schema. However, it lacks details on authorization requirements, side effects (e.g., status change implications), and return values, leaving gaps.

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, front-loaded sentence that conveys essential purpose and a key behavioral detail. No wasted words, though it could be slightly expanded for completeness without losing conciseness.

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?

Despite having 10 parameters (including a nested object) and no output schema, the description provides minimal context. It does not explain the update mechanics, required permissions, or what happens after update (e.g., return of updated object). Significant information is missing for an AI agent to use this tool effectively.

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 10% (only 'id' is described). The description adds no parameter-level information; it does not explain what each field (title, slug, status, etc.) does or how they interact. Given the low baseline, the description should compensate but fails to do so.

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 uses a specific verb ('Update') and resource ('existing WordPress page'), clearly distinguishing it from sibling tools like wp_create_page (create) and wp_delete_page (delete). The addition of 'creates snapshot before update' further clarifies behavior, making the purpose unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., wp_update_post) or when not to. The description only states what it does, leaving the agent to infer usage context. Given the presence of sibling tools for posts and pages, some direction would help.

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