Set Theme Mods (Kadence/Customizer)

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

Although annotations already mark destructiveHint=true, the description goes further by explaining that theme_mods control 'header/layout/colors' and that removing a key 'resets it to the theme default'. It also recommends backup steps, adding practical risk awareness beyond the structured annotations.

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 well-structured and front-loaded, starting with the core purpose, then prerequisites, a caution, and a compact Args list. Every sentence contributes useful information without padding or 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?

Given the tool's mutation and destructive potential, the description covers prerequisites, admin requirement, destructive effects, recommended pre-read/backup steps, parameter meanings, and return value. Since there is no output schema, the 'Returns' line adequately communicates the response shape. This is a complete operational picture.

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 input schema covers all three parameters with 100% description coverage, so the baseline is 3. The description's Args section largely restates the schema, though it does clarify that 'mods' is a key:value object and 'remove' resets keys to defaults. No substantial new parameter meaning is added beyond 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?

The description clearly states a specific verb and resource: 'Set and/or remove the active theme's theme_mods', distinguishing it from the read-only sibling wp_get_theme_mods. It also specifies the domain (Kadence/Customizer) and a required plugin, making the tool's scope 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 clear usage context by noting the required companion plugin, admin privileges, and a 'CAUTION' to always read current values with wp_get_theme_mods and back them up before bulk changes. It does not explicitly enumerate when-not-to-use alternatives, but it gives a strong paired-workflow hint.

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