deploy_site

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

With no annotations, the description carries full burden. It explains files are staged, uploaded incrementally (only missing bytes), and served via CloudFront. It also notes pricing ('Free with active tier'). Could mention auth or rate limits but provides good behavioral context for a static deploy.

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?

Three sentences, each adding value: what it does, how it works, and cost. No wasted words, major points upfront.

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 and 3 parameters, the description covers the deployment process, transport mechanism, and result (unique URL via CloudFront). Could mention project requirement but described in schema. Lacking error handling or edge cases, but adequate for a simple tool.

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 parameters are already documented. The description adds that files are 'inline file bytes' but doesn't elaborate on parameter details beyond what the schema provides. Baseline 3 is appropriate.

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 states 'Deploy a static site (HTML/CSS/JS) from inline file bytes' with specific verb and resource. It details the process of staging, uploading via plan/commit transport, and serving via CloudFront, differentiating it from sibling tools like deploy_site_dir which likely use directory paths.

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?

No explicit guidance on when to use this tool versus alternatives such as deploy_site_dir or deploy_function. The description implies it is for static sites with inline files but lacks when-to-use or when-not-to-use advice.

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