wp_activate_theme

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Switch' and repeats the input requirement, without mentioning side effects, persistence, prerequisites such as the theme being installed, or what the response will look like. This is a mutating operation that could affect the entire site, so more transparency is warranted.

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 two short sentences with no filler. The core action is front-loaded, and the parameter guidance is immediately useful.

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?

The tool is simple (one parameter, no nested objects), but the absence of an output schema and annotations leaves gaps: the description does not state expected return data or the prerequisite that the theme must already be installed. It is minimally viable but not fully complete.

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 already fully describes the lone parameter ('slug') with an example, and the description merely restates 'theme slug (directory name)'. With 100% schema coverage, the description adds no meaningful semantic value beyond baseline.

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 states a specific verb ('Switch') and resource ('active WordPress theme'), making the tool's purpose immediately clear. It also differentiates from sibling tools like wp_list_themes, wp_search_themes, and wp_install_theme by targeting the active theme rather than discovery or installation.

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 context: use this tool when you need to change the currently active WordPress theme. It does not explicitly name alternatives or exclusion conditions, but the active-theme framing implies the theme should already be installed, which is sufficient guidance for selecting this tool over install/search/list siblings.

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