download_bundle

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

No annotations are provided, so the description carries full burden. It only states the action and contents, but fails to disclose behavior such as whether it overwrites existing files, requires authentication, has size limits, or what the return value is. This is minimal transparency.

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 concise (two sentences), front-loaded with the main action, and includes a useful sibling pointer. Every sentence serves a purpose without redundancy.

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 tool has a side effect (saving a file) and no output schema, the description should at least mention the result or confirmation. It does not address return value, error conditions, or expected behavior after download. However, the purpose and contents are well covered, so it is moderately complete.

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 the context 'ZIP bundle' and 'local directory', but does not significantly extend understanding beyond the schema. The value added is marginal, meeting the baseline for high coverage.

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 action ('Download a Claude Design project as a ZIP bundle') and specifies the contents ('code, images, screenshots, uploads'). It also distinguishes itself from the sibling tool get_chats by stating that the ZIP does not include chat history.

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 provides clear context for when to use this tool (to download a project bundle) and explicitly recommends using get_chats for chat history separately. However, it does not contrast with other siblings like list_files or get_file, leaving some ambiguity about granularity.

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