wp_update_page

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

With no annotations, the description must disclose behavioral context. It does disclose the authentication prerequisite (WP_USERNAME/WP_APP_PASSWORD), but it remains silent about side effects, error behavior, and what fields are updated or returned, so transparency is incomplete.

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?

Two concise sentences with no filler; the purpose is front-loaded and the credential requirement is a separate necessary note. Every sentence earns its place.

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 no annotations, no output schema, and four parameters, yet the description only covers purpose and one prerequisite. Given the large sibling set and sparse schema, an agent lacks enough context to select and invoke this tool confidently without additional inference.

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% and the description adds no meaning for id, title, status, or content. The schema's names and enum provide some structure, but the description does not compensate for the low coverage, so an agent gets no parameter semantics beyond raw property names.

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?

States a clear verb ('update') and resource ('existing WordPress page'), so an agent can tell this is a mutation targeting pages rather than posts or media. However it doesn't explicitly contrast with sibling tools like wp_create_page or wp_update_post, so it earns 4 rather than 5.

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 when-to-use or alternatives are given; the word 'existing' weakly implies it is for updating already-created pages rather than creating new ones. The credential requirement is a prerequisite but not guidance for choosing among wp_create_page, wp_delete_page, or wp_update_post.

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