Deploy WordPress theme

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

Annotations already flag the operation as non-readOnly and destructive, so the description only needs to add context. It provides some useful context about the source directory and optional post-deployment activation, but doesn't disclose what deployment changes on disk, whether it overwrites an existing theme, or other side effects. This is adequate but not rich.

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, front-loads the main action, and contains no filler. Every phrase contributes to understanding the action, and the structure is clear and scannable.

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?

For a destructive deployment action, the description lacks workflow context—it doesn't mention that the theme must have been uploaded first (e.g., via an upload URL), what happens to the existing theme, or what a successful response looks like. The sibling set includes several theme-related tools, but the description doesn't help the agent choose or sequence them, and there is no output schema to fill the gap.

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 description coverage is 100%, so the baseline is 3. The description's references to an uploaded directory and optional activation mirror the schema descriptions for theme_path and is_activated without adding new detail, so there is no uplift.

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 clear action ('Deploy a WordPress theme') and a specific source condition ('from an already uploaded directory'), which helps distinguish it from theme installation or activation tools. It doesn't explicitly contrast with sibling tools like hosting_deployWordPressPlugin or hosting_activateWordPressThemeV1, so it stops short of a 5.

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 implies the tool is for themes already present in the website's directory and mentions the optional activation flag, but it doesn't state when to prefer this over install/activate variants or mention prerequisites like uploading the theme first. There is no explicit when-to-use or when-not-to-use guidance.

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