wp_update_settings

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

With no annotations, the description carries the full behavioral burden. It does not say whether omitted fields are preserved or cleared, whether this overwrites global or per-site settings, what permissions are needed, or whether the change is reversible — all material for a mutation tool.

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 short sentence with no filler and the verb-resource pair front-loaded. It is efficient, though the terseness is achieved by omitting needed information rather than by tight editing.

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 four-parameter mutation tool with no annotations and no output schema, the description is too thin. It never mentions which settings are mutable, that site is required, or how the update behaves, leaving the agent dependent on the schema alone.

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 100%, so every parameter (site, title, description, timezone_string) is already documented. The description adds no format, constraint, or default information beyond what the schema provides, so the baseline of 3 applies.

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 a specific verb and resource (update WordPress site settings), which is clear enough on its own. However, it offers no differentiation from the many sibling settings-mutation tools (legal_update_settings, seo_update_settings, fields_update_settings, mcp_set_option), so an agent cannot tell which scope applies without inspecting schemas.

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?

There is no guidance on when to use this tool versus wp_get_settings, mcp_set_option, or the other settings updaters. No prerequisites, no exclusions, and no stated relationship to list_sites despite site being required.

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