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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/mutation profile is covered by structured data. The description adds the useful detail that content is fetched remotely from a public URL, but omits what 'destructive' means here (does it replace existing draft media?), size/type limits, and failure behavior on unreachable URLs.

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?

A single sentence with the action, source, supported formats, and target all front-loaded; no redundant or filler 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?

For a destructive mutation with no output schema, the description covers the basic mechanics but not the consequences (overwrite vs append of existing draft media) or the effect on draft state. It is adequate but leaves the main behavioral question unanswered.

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 100%, so all five parameters including the enum for type are already documented in the schema. The description adds only the media-type enumeration and URL source context, which the schema largely conveys; baseline 3 applies.

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 states a specific verb and resource ('Downloads a media file from a public URL and attaches it to an existing draft'), which is precise and agent-actionable. It does not name or differentiate itself from the sibling set_draft_media_from_base64, which is the closest alternative, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus set_draft_media_from_base64 or update_draft. The parenthetical 'e.g. from Canva' hints at the source scenario but does not state conditions, prerequisites (media must already exist in a draft), or exclusions.

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