hosting_importWordpressWebsite

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

With no annotations, the description discloses key behavioral traits: automatic extraction, expected completion time, username auto-resolution, and potential long wait for larger sites. It does not contradict any annotations as none are present.

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 5 sentences, front-loaded with the purpose, and each sentence adds value. It is concise without redundancy, though it could be slightly more compact.

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?

Given no output schema, the description adequately covers the tool's behavior and results (extraction, availability time, username resolution). It is complete enough for an agent to understand the tool's function and outcome.

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% with detailed parameter descriptions, so baseline is 3. The description adds minimal extra meaning beyond the schema, only restating that an archive and database are uploaded. It does not provide new semantic insights.

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 it imports a WordPress website from an archive and database dump to a hosting server. It differentiates from sibling deployment tools (e.g., hosting_deployWordpressTheme, hosting_deployStaticWebsite) by focusing on complete WordPress site import, though it lacks explicit distinction from hosting_createWebsiteV1.

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 notes the process may take a while but provides no explicit guidance on when to use this tool versus alternatives like hosting_createWebsiteV1 or other deployment tools. It does not state prerequisites or situations where this tool should be avoided.

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