deploy_files

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

Annotations have destructiveHint=true; description confirms overwrite behavior and adds 'confirm with user'. No contradictions. Also discloses that tool returns version and status, and does not write to disk.

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?

Well-structured with two clear paragraphs. First paragraph covers usage and result; second covers anti-pattern. Slightly verbose but every sentence adds value.

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?

Covers prerequisites, output (version/status), post-action (get_site for URL), destructive behavior, and anti-patterns. No output schema but description compensates.

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 already covers all parameters (100% coverage). Description adds extra guidance: for files array, suggests index.html for HTML sites and clarifies single file use; for partition, explains default behavior.

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?

Clearly states verb 'publish' and resource 'file contents to a Hostsmith site'. Distinguishes from sibling `deploy_create_upload` by explicitly excluding binaries. Also sets context: 'without writing to disk' and 'when you have just generated 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?

Explicitly states when to use: after generating content and user wants it live. Prerequisites: site must exist (use create_site). Warning about overwriting with confirmation. Anti-pattern section clearly says when NOT to use and directs to `deploy_create_upload` for binaries, including escalation path.

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