publish_site

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the automatic CDN cache purge side effect, which is important. However, it does not specify whether deployment overwrites existing files, deletes omitted files, or what happens on failure, leaving some behaviors implicit.

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 four short sentences, all essential. It front-loads the main purpose, describes the input format, mentions a key side effect, and provides a concrete example. No unnecessary words.

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 tool with 3 parameters and no output schema, the description covers purpose, usage, side effect, and an example. It lacks details on return values or error behavior, but these are less critical for a conceptually simple deployment tool. Overall, it is sufficiently 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?

The input schema already covers 100% of parameters with thorough descriptions. The description adds minimal semantic value beyond referencing the file-to-content map and cache purge, which are already documented in the schema. The baseline of 3 applies here.

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 'Deploy multiple files to a website in one call' with a specific verb and resource. It also distinguishes from siblings like upload_file (single file) and purge_cache by emphasizing multiple files and automatic CDN cache purging.

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?

Provides usage context by stating 'This is the best way to publish or update a website' and gives an example. It implies batch deployment as opposed to single-file upload but does not explicitly name alternative tools or state when not to use it.

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