wp_delete_option

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

With no annotations, the description carries the full burden of behavioral disclosure. It states it 'Delete(s)' but does not disclose that this is a destructive, likely irreversible action, whether the option must exist, or what happens if the key is not found. The description is factual but omits any side effects or prerequisites.

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 a single, front-loaded sentence that states the action and resource without wasted words. It is appropriately sized for a simple delete operation and easy to scan.

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 destructive tool with no output schema and no annotations, the description is minimal. It fails to mention expected return values, error behavior, or the irreversibility of the operation. An agent would lack context on what constitutes success or failure, making the tool incomplete from an operational standpoint.

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 schema covers 100% of parameters (only 'key') and describes it as 'Option key to delete'. The description adds no additional meaning beyond that, such as format constraints or case sensitivity. Since schema coverage is high, the baseline of 3 is appropriate.

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 action ('Delete'), the resource ('WordPress option'), and the specific mechanism ('by key'). It distinguishes from sibling tools like wp_get_option and wp_set_options by specifying deletion, and from wp_delete_content and wp_delete_plugin by naming 'option' as the target.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that this is the destructive counterpart to wp_set_options, nor any conditions that should prompt its use (e.g., when an option is no longer needed). There is no discussion of exclusions or prerequisites.

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