Pull project files to disk

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

With no annotations, the description carries the transparency burden. It discloses 'preserving paths' and 'handles binaries', which are useful behavioral traits. However, it does not state whether existing local files are overwritten, whether directories are created, or what happens if both paths and prefix are provided. These gaps leave key behaviors unexplained.

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 two sentences, front-loaded with the core action. Every phrase adds value: 'Download files', 'into a local directory', 'preserving paths', 'handles binaries'. There is no fluff or repetition.

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?

Given the moderate complexity (4 params, no annotations, no output schema), the description is understandably brief but leaves out important context: what happens on local conflicts, whether the destination is created, and what the function returns. The schema partially compensates for parameter details, but the overall tool behavior is not fully specified.

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 75% (three of four parameters described), so the baseline is 3. The description adds no direct parameter details beyond what the schema provides. It relates indirectly via 'preserving paths' to the paths/prefix semantics, but does not clarify the relationship between paths and prefix or the default behavior when both are absent.

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 uses a specific verb ('Download') and clearly names the resources ('files from a Claude Design project') and destination ('local directory'). It distinguishes from siblings like write_files (upload), list_files (list), and read_file (read single file) by emphasizing the pull/download direction and adding 'preserving paths' and 'handles binaries'.

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 clearly communicates when to use the tool: when you need to download project files to local disk. It implies context but does not explicitly name alternatives or exclusions (e.g., 'for uploading use write_files'). The purpose statement alone is enough to infer usage, but missing explicit 'when not to use' guidance.

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