wp_set_options

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

With no annotations, the description carries the full burden. It usefully discloses that multiple options can be set at once and that sensitive options like siteurl and admin_email are blocked for security. However, it does not explain the consequences of hitting a blocked option, whether the operation is atomic, permission requirements, or what is returned on success/failure.

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 short sentences with no filler. The first states the purpose, the second gives the payload shape, and the third provides an important security constraint. Every sentence earns its place and the key information is front-loaded.

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 tool with a single parameter, no output schema, and no annotations, this is nearly complete: it covers what to pass and warns about blocked options. It falls short only by omitting response/error behavior and what happens when a blocked option is requested in a multi-option call.

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%, and the schema already describes the options parameter with an example. The description reinforces the key-value format and adds the 'one or more' batching cue, but it does not meaningfully extend the schema's semantic content.

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 states the verb 'Set' and the resource 'WordPress options', and 'one or more' clarifies the batching capability. This distinguishes it from sibling tools like wp_get_option, wp_get_options_batch, and wp_delete_option without requiring schema inspection.

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?

The usage is implied by the verb 'Set' and the instruction to provide key-value pairs, so an agent can infer when to use it. However, it does not explicitly mention alternatives or say when not to use it; the blocked-options note is the only exclusionary guidance.

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