Update site settings

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

Annotations already carry readOnlyHint=false, but the description adds real value: changes are global and take effect immediately for every visitor, with concrete ripple effects (homepage changes, date shifts), plus the Administrator-account requirement. No contradiction with annotations — the openWorldHint=true aligns with the described global reach.

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?

Three tight sentences with no filler: core purpose front-loaded, followed by impact examples, then the auth requirement. Slightly condensed but 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?

For an 18-parameter mutation tool, the description plus 100%-coverage schema and readOnlyHint=false annotation cover the essential call context: what it does, why it matters, who may call it. Minor gaps remain (no mention of persistence to wp_options or return format), but the safety profile is already carried by annotations.

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 coverage is 100%, so the baseline is 3. The description compensates by deepening meaning for the highest-impact parameters (show_on_front/page_on_front change the homepage; start_of_week/timezone shift displayed dates), which goes beyond their schema descriptions. The remaining 14 params are adequately covered by the schema.

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 specific verb+resource ('Update the site's core settings') and clarifies scope with concrete examples (homepage, timezone). It implicitly distinguishes itself from read-only siblings like get_site_settings by emphasizing 'global... for every visitor', though it never names an alternative explicitly.

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 context (global, immediate-effect settings) but no explicit when-to-use vs alternatives or exclusions. It doesn't distinguish itself from set_option, which could also mutate WP configuration, leaving the agent to infer boundaries between the two.

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