wp_delete_option

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

With no annotations present, the description carries the full burden of disclosing side effects, and it does so thoroughly. It explains irreversibility, impact on plugin settings and site behavior, the no-op result for nonexistent options, dry-run behavior, and production safeguards.

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 dense but mostly well-structured, leading with the core action and then covering important caveats and usage details. Some phrasing, such as 'Read it with wp_get_option and keep the value first,' is slightly awkward but not confusing enough to hurt clarity significantly.

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?

Given the lack of annotations and output schema, the description provides substantial context: destructive consequences, dry-run behavior, no-op reporting, required permissions, and production guard. It does not describe the output format in detail, but it covers the information most needed to use the tool safely and correctly.

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 description explains dry_run and allow_prod clearly, but the required parameters name and install are not explicitly described. While name is fairly inferable as the option name and install may be contextually understood, the description does not fully compensate for the 0% schema coverage.

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 tool deletes a wp_options row entirely and explicitly contrasts it with setting the option to empty, which distinguishes it from wp_set_option and other option-related tools. The verb and resource are specific and unambiguous.

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 description provides practical usage guidance by warning against using this for setting an empty value, pointing to wp_get_option for reading values first, and explaining the dry_run default and the need to pass dry_run=false to actually delete. It also mentions required environment and permission conditions, though it does not explicitly say 'use this when permanent deletion is intended'.

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