Upload media from URL

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

Annotations already declare the write (readOnlyHint=false), external reach (openWorldHint=true) and non-idempotency. The description adds meaningful context beyond them: the source must be a public URL, and the result is a persisted media object in the library that can be chained into post creation. It omits size/type limits and duplicate-on-repeat behavior, so not a 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?

Two tight sentences: purpose first, downstream chaining second. No filler, no restating the tool name.

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 no output schema, the description correctly summarizes the return value (a media object) and how to use it, which is what an agent needs for this single-parameter import. Minor gaps on limits and repeat-call behavior keep it from a 5.

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?

Only one parameter and schema coverage is 100%, and the schema already documents it as a 'Public HTTPS URL of the image or video to import.' The description repeats the 'public URL' idea without adding syntax, size, or format guidance, so it meets the baseline but adds no new meaning.

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 (download/store) and resource (image or video media into the PostSider media library) and clearly separates this import action from sibling tools like postsider_create_post or the list/get tools. An agent knows this is a URL-to-library ingest, not a post creation.

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 forward-looking usage context by naming the downstream step: pass the returned media object (or array) as `images` to postsider_create_post. It does not state when not to use it (e.g., local file upload path) or the public-URL-only restriction as an exclusion, but the triggering condition is clear.

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