wp_update_page_seo

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 important side effect of creating a snapshot before updating, which hints at recoverability. It does not address whether fields are merged or replaced, permissions required, or what a successful update returns.

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?

A single front-loaded sentence states the action, scope, plugin, and safety side effect with no filler. Every word contributes meaning.

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 low-complexity two-parameter tool, the definition plus schema covers how to choose fields and what resource is being updated. It is still incomplete for a mutating tool with no annotations and no output schema, because it does not describe the response format, merge vs. replace semantics, or how to use the created snapshot for rollback.

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?

The schema adequately documents the 'fields' parameter and directs agents to the wp_get_page_seo catalog for allowed keys. The tool description additionally clarifies that the target is a page or post, which is crucial semantics for the otherwise undocumented page_id parameter.

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 names the exact operation ('Update SEO fields') and resource ('a page/post via All in One SEO'), clearly distinguishing it from generic wp_update_page and read-only wp_get_page_seo. It also adds a notable side effect ('creates snapshot before update') that helps differentiate it from similar update tools.

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?

Usage context is implied: an agent should call this when updating All in One SEO fields for a page or post. However, it does not explicitly state when to prefer this over wp_update_page, and it relies on the schema parameter description to point the agent to wp_get_page_seo for allowed field keys.

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