Deploy Site

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

Annotations already declare destructiveHint=true / idempotentHint=false, and the description adds the concrete consequence: files at the same path are replaced, so prior content is lost. It also discloses size limits (≤10MB per call), accepted file types, rejection of server-executable types, and automatic parent-directory creation.

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?

Front-loads the core action and constraint data, then the routing/consent guidance. Every sentence carries information, though the final sentence is long and could be split for readability. No filler.

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 operation, encoding, path semantics, size limit, file-type restrictions, host-state prerequisite, destructive overwrite behavior, and agent routing/consent behavior. With no output schema needed for an upload tool, nothing material is missing.

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, but the description adds real meaning beyond the schema: base64 encoding of content is restated helpfully, path values may include directories, and missing parents are auto-created. The ≤10MB total constraint on files is also a semantic constraint the schema lacks.

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?

States a specific verb (upload) and resource (static files to a domain's Secure Static Hosting), and is clearly distinguishable from siblings like delete_hosting_file, make_hosting_dir, and create_hosting. An agent can identify the operation without opening the schema.

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 the prerequisite (hosting must be ACTIVE; check get_hosting first), the alternative to avoid (giving dashboard upload steps), the trigger context (building/editing a site for a Porkbun domain), and the consent requirement (get their OK first). This is about as complete as usage guidance gets.

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