Deploy a local directory

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

With no annotations, the description reveals some behaviors (recursive upload, single connection, glob application, dry_run) but omits details like default excludes, error handling, permission requirements, and return values. The mention of default excludes is helpful but incomplete.

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 concise sentences front-load the main action and critical features (recursive upload, connection, globs, dry_run). No wasted 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?

The description covers the main functionality for a moderately complex tool (6 params, no output schema), but lacks details on default excludes, error behavior, and return values. It does not fully compensate for missing annotations.

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% with clear parameter descriptions. The description adds context about recursion and glob behavior, but adds little beyond the schema's own descriptions. Baseline of 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 clearly states the verb 'upload' and the resource 'local directory', and highlights key features: recursive, single connection, exclude/include globs, dry_run. It distinguishes from sibling tools like ftp_upload (single file) and ftp_download.

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 description implies usage for bulk deployment via 'recursively upload a local directory' and 'over a single connection', but does not explicitly state when to use versus alternatives. No when-not or exclusion guidance is provided.

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