Deploy WordPress Theme

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

With no annotations, the description carries the burden of disclosure. It states the core actions (uploads theme files, optionally activates) but does not mention whether it overwrites existing themes, required permissions, or failure behaviors. This is partial transparency but leaves important side effects undisclosed.

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 concise and front-loaded, using two short sentences. The first sentence states the main purpose and the second clarifies the optional activation, with no wasted words.

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 deployment tool with 5 parameters and no output schema, the description provides a basic overview but lacks details on prerequisites (e.g., where the archive must reside), the format of the archive, and what happens upon successful deployment. It is adequate but not thorough.

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 parameters with descriptions (100% coverage), so the baseline is 3. The tool description adds no extra meaning beyond the schema, simply referring to 'directory/archive' which aligns with archive_path.

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 uses a specific verb ('Deploy') and resource ('custom WordPress theme from a directory/archive'), clearly indicating its function. It also distinguishes itself from sibling tools like hosting_deploy_wp_plugin and wp_themes_install by emphasizing 'custom' and 'directory/archive'.

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 when to use this tool: when deploying a custom theme from a directory or archive. It provides clear context but does not explicitly mention alternatives or when not to use it, such as for themes from the WordPress repository.

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