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

Annotations already establish read/write/idempotent/non-destructive hints, and the description adds useful behavioral context: the file must be publicly shared, Drive/Dropbox links are auto-converted, and there is a 50 MB limit. It does not describe failure behavior or response shape, but for a one-parameter tool with strong annotations this is adequate.

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?

Four sentences, each earning its place: purpose, when to skip, when to use, and prerequisites. The guidance is front-loaded and reads naturally; the mild repetition of the media_id reuse idea is not enough to count as waste.

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 simple, one-parameter tool with no output schema, the description is complete: it names the returned object (media_id), explains the common alternative path, and gives the operational constraints (public sharing, automatic Drive/Dropbox conversion, 50 MB limit). No important decision or invocation detail is missing.

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?

The schema already documents the single url parameter as a direct, publicly reachable https link, so the baseline is 3. The description adds meaning beyond the schema by noting that Google Drive and Dropbox share links are accepted/converted and by specifying the 50 MB file limit.

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 uses a specific verb plus resource ('Download an image or video from a public link into sprkly and get a media_id back') and immediately differentiates from the sibling sprkly_schedule_post by clarifying when the tool is NOT needed. This makes the tool's purpose unmistakable.

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?

It explicitly tells the agent when not to use it ('You usually do NOT need this'), names the alternative (sprkly_schedule_post with media_urls), and states the specific condition for using this tool ('only when the user wants one media_id to attach to more than one post'). It also adds sharing and size prerequisites.

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