Deploy JavaScript application

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

Annotations already mark the operation destructive and non-read-only; the description adds useful behavior: the server automatically triggers a build, upload credentials are generated internally, and the tool is end-to-end. It does not disclose what is overwritten or destroyed (e.g., whether a previous deployment on the domain is replaced), which would have made this a 5, but it gives meaningful workflow context beyond the annotations.

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?

Four sentences, each serving a purpose: action, archive constraints, automatic build, upload handling, and post-deploy status tracking. Slight redundancy with the archivePath schema description and the repeated 'IMPORTANT' caps keep it from a 5, but the structure is front-loaded and efficient.

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 mutation tool with no output schema, the description tells the agent what to do after calling it (use hosting_listJsDeployments) and what prerequisites to satisfy before calling (clean archive). It omits specifics on destructive effects and error paths, but the schema and annotations cover parameters and destructiveness, so the core calling context is complete.

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 description coverage is 100%, so the baseline is 3, and the description largely repeats the schema constraints rather than adding new parameter meaning. It re-emphasizes the source-only archive rule and supported formats in archivePath, but domain and removeArchive semantics come from the schema.

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?

Opens with a specific verb+resource: 'Deploy a JavaScript application from an archive file to a hosting server.' It distinguishes itself from static-site/PHP/WordPress deploy siblings mostly by application type and the mention of an automatic build process, but it never explicitly names a sibling or states the boundary (e.g., static vs Node), so it is clear but not perfectly differentiated.

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?

Gives actionable preparation guidance (source-only archive, skip node_modules, honor .gitignore), explicitly instructs not to call a separate upload-url endpoint, and routes the agent to hosting_listJsDeployments for status. It does not enumerate alternatives like hosting_deployStaticSiteArchiveV1 or hosting_deployPhpApplication, so it falls short of fully explicit when-to-use-this-vs-that guidance.

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