Deploy Static Site

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

The description goes beyond annotations by disclosing specific behaviors: it uploads only files Cloudflare doesn't already have, applies _headers/_redirects as configuration rather than uploading them, supports .assetsignore rules, and notes that newly created sites are served on workers.dev. This complements the destructiveHint and openWorldHint annotations with concrete operational details.

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 core purpose, and every sentence adds distinct operational detail without redundancy. It is concise yet information-dense.

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 deploy action with no output schema, the description adequately covers input meaning, side effects, and special file handling. It provides enough context for an agent to select and invoke the tool correctly without significant gaps.

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 extra value by explaining how not_found_handling relates to SPAs and how directory contents like _headers/_redirects and .assetsignore are treated, which is not fully captured in 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?

The description clearly states the tool deploys a local directory as a static site (assets-only Worker) on Cloudflare Workers, using a specific verb and resource. It distinguishes itself from sibling tools like deploy_worker or redeploy_assets by emphasizing assets-only and incremental upload behavior.

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 when to use this tool (deploying static sites) and includes practical guidance like setting not_found_handling for SPAs. However, it does not explicitly name alternative tools or exclusions, so the guidance is implied rather than direct.

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