wp_set_setting

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

Discloses important behaviors: dry_run defaults to true, value verification against actual stored value, and the encoding of special characters. No annotations are present, so the description carries the full burden and handles it well.

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 well-organized, using line breaks and backticks for clarity. Each sentence adds meaningful information without redundancy.

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?

Covers the essential edge cases (dry-run, production safety, encoding, invalid keys) and the write verification behavior. No output schema is provided, but the description hints at the response shape by mentioning the actual stored value is returned.

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 the semantics of key, value, dry_run, and allow_prod in detail. However, the 'install' parameter is never mentioned in the description, leaving a gap for that required parameter.

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?

Clearly states it changes one site setting, distinguishing from wp_get_settings. The specific verb 'Change' is appropriate and the resource is clear.

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?

Explicitly describes accepted keys, the dry_run default behavior, and the allow_prod requirement for production writes. Sibling tools like wp_get_settings are implied context, though not directly named as alternatives.

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