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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description earns credit by adding real behavior: the 25 MiB ceiling for fonts/SVG/JSON and the returned durable asset ID and verified SHA-256 hash. It omits auth requirements and deduplication/overwrite semantics beyond what the schema hints at.

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?

Two sentences, zero filler, with the import scope and source constraint front-loaded before the return value and size limit. Every clause carries information an agent needs.

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?

An output schema exists, so the return values need not be elaborated, and annotations cover the safety profile. For a 9-parameter import tool the description is adequate, though the defaults for autoTranscribe/autoSuggestShorts/autoProcessEnabled and the project/workspace targeting rules are left entirely to the 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 description coverage is 78%, so the schema already documents most of the 9 parameters, including contentHashSha256 and the auto* flags. The description adds only the accepted media-type list and the per-type size limit, which map loosely onto the url parameter; it says nothing about name, projectId/workspaceId scoping, or the auto-process toggles. Baseline 3.

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 (import) and resource (media from a direct URL) plus an enumerated set of supported media types, which implicitly separates it from media_upload_file/media_upload_start. It never names an alternative sibling, so differentiation is inferable rather than stated.

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?

Usage is only implied: 'from a direct URL' suggests picking this over the file-upload siblings when the source is a URL. There is no explicit when-to-use, no prerequisite (e.g. URL must be publicly reachable), and no exclusion guidance.

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