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

Annotations only declare the generic write/open-world/no-destroy profile; the description adds the operational specifics an agent actually needs: the 500 MB ceiling, that the asset lands at the workspace root and location-scoped keys are refused, and the required media.create permission. That is exactly the beyond-annotation context this dimension rewards.

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?

Five compact sentences, each with a distinct job: what it does, what it returns, when to use it, its limit plus the alternative, and its constraints. The purpose and scope are front-loaded with zero filler.

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?

With an output schema present, the description need not explain return values in depth, and it still names them briefly. Size limit, permission requirement, placement rule, and alternative tools cover everything an agent needs to call this correctly and to avoid mis-calling siblings.

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 the schema already documents url, name, tags and folderId, including the root-filing default. The description reinforces the root-placement behavior but adds no syntax, format, or default detail the schema lacks. 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?

States a specific verb and resource ('Copy a file from a public URL into the media library'), and explicitly contrasts itself with create_web_link ('show a live web page rather than copy a file') and mint_upload_url. An agent can distinguish it from every near sibling without opening a schema.

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?

Gives a concrete use case ('migration: pull from a Drive share, S3, an old CMS export'), an explicit size boundary with the alternative for exceeding it (500 MB cap, use mint_upload_url for larger), and a routing rule away from create_web_link. When-to-use, when-not, and alternatives are all present.

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