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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the description's job is to add nuance, which it does: it explains the upload-domain validation constraint and that the result is { id, path } or { error }. It does not cover size/type limits, overwrite or duplicate behavior, which would be needed for a full 5.

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?

Effectively three sentences with the primary action and the local-file exclusion front-loaded. Slightly dense with nested parentheticals from the API URL and the img-src aside, but nothing is wasted.

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?

A single required parameter plus an output schema means little needs explaining, and the description covers what it returns (id, path) and the failure shape { error }. The only gap is operational limits on the upload itself.

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% and the schema already says 'public http(s) URL; local files and private hosts not supported'. The description largely restates this constraint, adding only the framing of why (upload-domain validation), so 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 ('Upload a remote image or video into the media library from a public http(s) URL') and immediately scopes it against local/private files. It is clearly distinguishable from siblings such as uploadWidgetTool and mediaListTool.

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 an explicit when-to-use trigger ('before scheduling a post when the user provides an external media URL not already hosted on our domain') and an explicit when-not ('Local or private files cannot be fetched by this tool'), naming the alternative public API endpoint as the escape hatch.

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