agency-hosting_importWebsiteFromArchiveV1

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

With no annotations provided, the description correctly carries the transparency burden by disclosing that website contents are overwritten and listing supported archive types. A minor ambiguity exists between the description's 'root directory' and the schema's '.h5g/' directory, but the key destructive behavior is clear.

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 three sentences, front-loaded with the main action, followed by a prerequisite, a destructive-effect warning, and supported formats. Every sentence contributes necessary operational information without padding.

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 two-parameter tool with no output schema and no annotations, the description is unusually complete: it explains the required upload prerequisite, the overwrite consequence, and valid archive formats. It could be strengthened by reconciling the directory wording with the schema, but overall it is sufficient.

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%, so the baseline is 3. The description adds value by explicitly enumerating supported archive extensions (.zip, .tar, .tar.gz, .tgz) and reinforcing that the archive filename must correspond to an already-uploaded file.

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 and resource: 'Imports an Agency Plan website from an already-uploaded archive.' It clearly distinguishes this from siblings like hosting_importWordpressWebsite by tying it to Agency Plan websites and an existing archive upload.

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 a clear prerequisite workflow: upload the archive via file browser first, then provide its filename. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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