Update WordPress Settings

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

Adds meaningful behavior beyond annotations: requires admin permissions (manage_options), partial update semantics ('Only the fields you pass are changed'), a limitation (cannot set blog_public via REST), and return value ('Returns the updated settings object'). No contradiction with annotations.

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 well-structured with a summary, usage example, caveat, Args list, and return statement. It is slightly repetitive with the schema's parameter list, but every sentence contributes useful context and the layout aids scanning.

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 an update tool with 8 optional parameters, the description covers permissions, scope, partial update behavior, limitations, and return format. This is complete given the schema already fully documents parameters and annotations provide safety hints.

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 covers all 8 parameters with descriptions, so baseline is 3. The description adds an example usage for static homepage and notes that page_on_front/page_for_posts are used only with show_on_front='page', but the Args list repeats schema info without adding much new semantic value.

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 identifies the tool as updating core WP general settings, listing specific fields (title, tagline, posts-per-page, front/blog page assignment). It distinguishes from siblings like wp_get_settings (read) and wc_update_setting (WooCommerce) by scope and verb.

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?

Provides explicit usage context with the static homepage example, and states when to avoid it (cannot toggle blog_public, recommends WP Admin or a plugin instead). This gives clear when-to-use and when-not-to-use guidance, though it doesn't name sibling alternatives directly.

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