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

Annotations already signal a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds genuinely useful traits beyond that: returns a stable hosted URL, is free, and has a 50MB size ceiling — none of which are in the annotations or schema.

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-loads the core action and the return value, then adds when-to-use and constraints. Three tight sentences with no filler; the example referenceImageUrl anchors the output without bloating the text.

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?

No output schema exists, and the description explicitly explains the return (a stable hosted URL usable as a reference image), plus cost and size constraints. The only material gap is the undocumented filename parameter, but overall the definition is sufficient to call the tool correctly.

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 coverage is 50%: url is documented and filename is not. The description reiterates that the URL must be public http(s) image/video (matching the schema), but says nothing about the filename parameter or how it affects the stored asset, leaving half the parameters undocumented in both description and 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+resource: fetch a public image/video URL and store it on VidGuy, returning a hosted URL. It also distinguishes itself from the upload siblings by scoping to URLs the asset isn't already hosted at, so an agent can tell it apart from create_upload/ai_edit_upload/swap_upload.

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?

"Use this when you have a URL but the asset isn't already hosted with us" gives a clear selection condition. It doesn't name the specific alternative tool to use when the asset IS already hosted, but the when-to-use is explicit and actionable.

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