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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds behavioral nuance not covered by annotations, such as the 'time-limited' nature of the download URL and the fact that it operates on 'previously uploaded' files. No contradiction with 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 extremely concise, consisting of two short sentences. It front-loads the tool's primary purpose and adds a separate note for bulk support, with no wasted words.

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?

The description covers the high-level purpose, return type (metadata + URL), and bulk capability. Annotations handle safety. However, with no output schema and no parameter explanations, gaps remain about what metadata is returned, how to obtain order_id/media_id, and URL expiration behavior. It is adequate but not complete.

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 only mentions 'order_ids' and 'media_ids' for bulk execution but does not explain the required 'order_id' and 'media_id' parameters or their relationship. This is insufficient given the complete absence of schema descriptions.

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 clearly states the tool's function with a specific verb ('Retrieves') and resource ('metadata and a time-limited download URL for a previously uploaded media file'). It differentiates from siblings by emphasizing 'previously uploaded' and mentioning bulk support, making the scope precise.

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 description provides clear context: use this to get metadata/download URL for a previously uploaded media file. It also notes bulk capability with order_ids and media_ids. However, it lacks explicit comparisons to alternative tools or when-not-to-use guidance, so it stops short of full exclusionary guidance.

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