mcp_install_theme

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

With no annotations provided, the description carries full burden of disclosure. It does not explain whether installation overwrites an existing theme, whether activation requires additional steps, or what the success/failure response looks like. The user is left to infer side effects.

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, clear sentence with no fluff. Every word serves a purpose, and the structure is optimally front-loaded for quick comprehension.

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 low complexity (2 parameters, no output schema, simple domain), the description adequately covers the core functionality. However, it could mention the expected behavior when the theme already exists or the activation process, but these are minor omissions for a straightforward install action.

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?

Schema coverage is 100%; the description adds no meaning beyond the schema's parameter descriptions ('Theme slug from WordPress.org', 'Activate after install'). Baseline score of 3 is appropriate as no additional value is provided.

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 ('Install'), resource ('theme'), source ('from WordPress.org'), and method ('by slug'). It effectively distinguishes this tool from siblings like 'mcp_install_plugin' (installs plugins) and 'mcp_install_theme_zip' (installs from a zip file).

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 no guidance on when to use this tool versus alternatives such as 'mcp_install_theme_zip' or 'wp_activate_theme'. It does not mention prerequisites like network activation permissions, potential conflicts with existing themes, or error scenarios (e.g., theme not found).

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