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

Adds substantial behavior beyond annotations: a 100 MiB size cap, prohibition on overwriting, required files:write and account permissions, handling of expired URLs, and retry inspection advice. These details are consistent with the non-destructive, non-idempotent, open-world annotations.

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?

Front-loaded with the core action and constraints, then auth and retry guidance. Every sentence carries operational meaning with no filler.

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?

Rich for a complex import tool with a oneOf schema and nested file object: size limits, source restrictions, permissions, and retry advice are all covered. The remaining gap is destination and naming parameters, but an output schema exists and annotations cover the safety profile.

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?

With 0% schema description coverage, the description must compensate. It explains the source_url versus file object choice and constrains the URL, but leaves folder_hash and file_name completely undocumented and does not explain the nested file object fields (file_id, download_url, mime_type).

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 new file from public HTTPS') along with scope (up to 100 MiB) and source modes (source_url or client file object). It implicitly differentiates from upload_file by forbidding local paths, but never names the sibling 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?

Gives clear when-to-use (public HTTPS, one of two source shapes) and when-not (no local paths, private IPs, credentials, overwrite). It adds recovery guidance for expired URLs and uncertain retries, though it does not name an explicit alternative tool for disallowed local uploads.

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