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

Annotations already flag this as destructive and not read-only; the description adds meaningful behavior beyond that: the returned token is one-time, the shell command must be run, only changed files transfer, and the token expires after 60 minutes. No contradiction with the annotations.

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?

Two sentences, with the main action and example front-loaded and the follow-up behaviors packed into the second sentence. Every sentence contributes information and there is 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?

The core invocation flow is complete: this tool prepares an upload, returns a runnable shell command, and the token has a clear expiry. With no output schema, the return behavior is described directly; the main gap is the unexplained `site`/`message` parameters, though the destructive mode is already covered by annotations and schema enums.

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 description coverage is only 33%, and the description does not compensate: it never explains the required `site` parameter or the optional `message` parameter. The 'local folder' phrasing relates to the workflow, not to any schema property, so the description adds almost no parameter-level meaning.

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 a specific action ('Prepare an upload of a local folder') and names the concrete output (one-time token and shell command), so an agent can tell it is a staging step rather than a direct file write. It does not explicitly contrast itself with sibling tools such as write_files or delete_files, so it misses the top score.

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 build-output example ('dist/') and 'only changed files are transferred' imply a deployment use case, but no when-to-use or when-not-to-use guidance is given versus alternatives like write_files or delete_files. The usage context is implied rather than explicit.

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