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

Annotations already indicate readOnly=false, idempotent=false, and destructive=false, but the description adds meaningful behavioral context: it owns reference management, returns asset IDs, preserves input order, and avoids generation or spending. It also clarifies expected failure-mode behavior on partial failure, which goes well beyond the 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?

The description is dense but every sentence carries operational value: purpose, ownership, return behavior, failure handling, prohibitions, and the alternative tool. It is front-loaded with the primary purpose and structured logically from what to do to what not to do.

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 tool with one parameter, no output schema, and rich annotations, the description is complete enough. It covers the input source, constraints, return semantics, failure recovery, prohibited actions, and the alternative path. No critical information an agent needs to invoke it correctly is missing.

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%, so the description must compensate. It explains the semantic meaning of download_url by saying files come from 'temporary host file handles' and warns against local filesystem paths or invented URLs. However, it does not explicitly describe file_id, file_name, or mime_type, leaving part of the nested object's meaning to inference from the 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?

The description uses a specific verb-resource pair: 'import up to eight user-authorized image, video or audio files... into the connected private MaxVideoAI library.' It clearly distinguishes this from create_reference_upload_link by naming the alternative and the condition that selects it. The scope and source of the files are explicit.

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?

It states exactly when to use this tool, when not to use it ('do not call list_media after a successful direct import'), and which sibling to use instead ('use create_reference_upload_link instead'). It also provides concrete retry guidance for partial failures, leaving no ambiguity for an agent.

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