Install a theme

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

The annotations already flag this as destructive, non-idempotent, non-read-only, and open-world, and the description adds meaningful context beyond them: no undo point is recorded, existing folders are not replaced, the result is an error, and specific WordPress capabilities can block the call. It also describes return fields, which helps the agent understand the outcome.

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 front-loaded: it leads with the action and non-activation behavior, then covers return data, permissions, failure conditions, and alternatives. Every sentence provides actionable information.

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?

Although there is no output schema, the description lists the key return fields and explains constraints, failure behavior, and alternative tools. For a one-parameter mutation tool, this provides everything needed to call it correctly.

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 documents the slug format and normalization rules at 100% coverage. The description reinforces that the slug comes from WordPress.org and mentions the returned stylesheet, but it does not add substantial parameter semantics 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 states a specific verb and resource: download and install a theme from the WordPress.org directory by slug. It immediately clarifies that activation does not happen, and it distinguishes this from ZIP installation and theme activation by naming the relevant sibling tools.

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?

It explicitly names alternatives: use wp_install_theme_zip for ZIP themes and wp_activate_theme to switch themes. It also states prerequisites and refusal conditions, including install_themes and DISALLOW_FILE_MODS.

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