import_file

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. It usefully discloses one non-obvious trait — bytes do not pass through model context — but says nothing about overwrite behavior, destination defaults, failure modes, or what is returned for a mutating import.

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 front-loaded sentence with no waste; the key constraint (no model-context routing) is stated immediately.

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 mutation tool with a nested-object parameter, no annotations, and no output schema, one sentence is far too thin. The agent knows why to use it but not how to populate file, destination, or overwrite, nor what to expect on completion.

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 4 parameters, including a nested required object (download_url, file_id) plus overwrite, destination, and cwd. The description adds no parameter meaning at all, so it fails to compensate for the entirely undocumented schema.

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 and resource (import a host-provided file into the Agent VM) and adds a distinguishing scope detail — the bytes bypass model context. An agent can separate this from read_file or present_file, though the exact boundary versus those siblings is not spelled out.

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 phrase 'without routing file bytes through model context' implies the use case (getting a large/host file into the VM without burning context), which is useful guidance, but no explicit when-to-use or alternative tools are named.

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