hosting_importWordpressWebsite

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

No annotations exist, so description carries full burden. It discloses time expectations, auto-extraction, and automatic username resolution. However, it does not mention if the operation is destructive (overwrites existing content) or required permissions.

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?

Five sentences, well-organized: purpose, steps, timing, auto-resolution. No redundant information. Each sentence serves a purpose.

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?

No output schema, but description explains expected outcome (extraction, availability in minutes). Missing explicit return value or status, but covers main flow adequately for a 3-param tool.

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%, but description adds valuable context: instructions for creating archive from directory with naming pattern, and that username is resolved from domain. This exceeds schema descriptions.

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 (import), resource (WordPress website), and method (from archive file). It distinguishes from siblings like fresh install or static deploy by specifying 'from an archive file' and mentioning database dump.

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 clear context for use: importing an existing WordPress site with archive and SQL dump. It lacks explicit when-not-to-use or alternatives (e.g., for static sites use other tools), but the context is sufficient.

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