Download a project file

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the fact that this writes to the local filesystem is already covered. The description adds 'any type' scope, but says nothing about overwriting an existing local file, creating parent directories, auth requirements, or size limits.

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?

A single efficient sentence with the resource and destination front-loaded and no filler. It is appropriately sized, though the brevity comes at the cost of missing behavioral detail.

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?

For a write-to-local-disk tool with no output schema, the description should cover overwrite semantics, directory handling, and what is returned on success; none of that is present, and one required parameter is undocumented in both description and schema.

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 67%: `project` and `localPath` are documented in the schema, but the required `path` parameter has no description anywhere. The description's phrase 'to a path on this computer' merely paraphrases localPath and leaves the remote `path` meaning unresolved.

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+resource: saving a project file of any type to a local path. This clearly separates it from upload_file (opposite direction) and read_file (returns content without saving), though it does not name those siblings explicitly.

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?

No when-to-use guidance, no prerequisites, and no mention of when a user should prefer read_file (read inline) over download_file (save to disk). The agent must infer the distinction from the name alone.

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