agency-hosting_buildWebsiteNodeJSAssetsV1

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

The description discloses that website contents are overwritten and that the build result is deployed to public_html, which are important side effects. No annotations exist, so the description carries full burden and does so adequately.

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 concise sentences with no redundant information, effectively covering the action, prerequisites, and outcome.

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?

It explains the process, prerequisites, and deployment destination. It doesn't mention build time or errors, but those are not critical for tool selection. Overall complete for the given context.

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 description clarifies the archive_path by specifying 'relative path from document root' and the prerequisite of uploading, adding value beyond the schema descriptions. website_uid is straightforward.

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 builds and deploys a Node.js application from an uploaded archive for an Agency Plan website, distinguishing it from other deploy tools that may not involve building or overwriting content.

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?

It provides a prerequisite (upload archive first) and explains the required parameter (relative path). While it doesn't explicitly compare to similar deploy tools, the context is sufficient for typical usage.

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