Remote Download

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

No annotations are provided, so the description carries the full behavioral burden and largely fails to. It does not say whether an existing local file is overwritten, whether the download is resumable, what permissions or connectivity are required, or what the call returns. Only the destination scope ('registered local project') is disclosed.

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?

One clean sentence with no padding, and the action is front-loaded. But the brevity comes at the cost of omission rather than efficiency; a single clause cannot cover destination-path behavior or overwrite semantics for a 3-parameter write tool.

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?

With no annotations, no output schema, 0% schema coverage, and no sibling differentiation, the description is too thin for a tool that writes to the local filesystem. An agent would have to open the schema and guess at overwrite, path-defaulting, and return behavior.

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 0% across three parameters, so the description must compensate and does not. 'remote file' loosely maps to remote_relative_path and 'local project' to project_id, but the optional local_relative_path — which clearly controls where the file lands and defaults to null — is never addressed, leaving its defaulting behavior unexplained.

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 (Download) and resource (a remote file) plus the destination (the registered local project), so the core action is unambiguous. However it does nothing to distinguish itself from the near-identical sibling ssh_download, leaving the agent to guess which download tool applies.

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 alternatives despite ssh_download, remote_read, and remote_stat sitting right next to it in the toolset. The only hint is the phrase 'registered local project', which weakly implies a project must exist first.

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