Import WordPress Website

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

With no annotations, the description must disclose its own behavior. It states that files are extracted and the site is deployed automatically, which is useful. However, it does not disclose potential side effects like overwriting existing files, permission requirements, or whether the operation is reversible, which is important for an import tool.

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 sentences with no redundant wording. It immediately states the purpose and includes the key behavioral outcome, making it easy to parse.

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 involves importing an entire WordPress site with four parameters, yet the description omits important context such as prerequisites, what happens to existing files, and the exact role of the optional SQL dump. It also doesn't clarify that sql_path is optional, creating potential ambiguity in interpreting 'database dump.'

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 covers all parameters with descriptions, so the baseline is 3. The description adds minimal semantic value beyond the schema, merely referencing 'archive' and 'database dump' which maps to archive_path and sql_path. It does not elaborate on the format, required structure, or the optionality of sql_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 clearly states the tool imports a WordPress website from an archive and database dump, and explicitly mentions the extraction and automatic deployment. This distinguishes it from sibling deployment tools like hosting_deploy_static or hosting_deploy_js_app.

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 gives clear context that this is for importing an existing WordPress site from backup files, implying it's for migration/restoration rather than fresh installation. However, it does not explicitly mention alternatives or state when not to use this tool, such as for a new site or when using agency_import_archive.

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